Method and System for Generating a Nuclear Reactor Core Loading Distribution

ABSTRACT

The generation of a nuclear core loading distribution includes receiving a reactor core parameter distribution associated with a state of a reference nuclear reactor core, generating an initial fuel loading distribution for a simulated beginning-of-cycle (BOC) nuclear reactor core, selecting an initial set of positions for a set of regions within the simulated BOC core, generating an initial set of fuel design parameter values utilizing a design variable of each of the regions, calculating a reactor core parameter distribution of the simulated BOC core utilizing the generated initial set of fuel design parameter values associated with the set of regions located at the initial set of positions of the simulated BOC core and generating a loading distribution by performing a perturbation process on the set of regions of the simulated BOC core to determine a subsequent set of positions for the set of regions within the simulated BOC core.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)).

RELATED APPLICATIONS

-   -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation of United States        patent application entitled METHOD AND SYSTEM FOR GENERATING A        NUCLEAR REACTOR CORE LOADING DISTRIBUTION, naming Nicholas W.        Touran as inventor, filed Nov. 21, 2013, application Ser. No.        14/086,474, which is currently co-pending, or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.    -   For purposes of the USPTO extra-statutory requirements, the        present application constitutes a continuation of United States        patent application entitled METHOD AND SYSTEM FOR GENERATING A        NUCLEAR REACTOR CORE LOADING DISTRIBUTION, naming Nicholas W.        Touran as inventor, filed Nov. 27, 2013, application Ser. No.        14/092,211, which is currently co-pending, or is an application        of which a currently co-pending application is entitled to the        benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

TECHNICAL FIELD

The present disclosure generally relates to the determination of anuclear fuel loading distribution for a nuclear core, and, inparticular, the determination of a nuclear fuel loading distribution fora beginning-of-cycle (BOC) nuclear reactor core.

SUMMARY

In one aspect, a method includes, but is not limited to, receiving atleast one reactor core parameter distribution associated with a state ofa core of a reference nuclear reactor; generating an initial fuelloading distribution for a simulated beginning-of-cycle (BOC) core of anuclear reactor; selecting an initial set of positions associated withina set of regions within the simulated BOC core of the nuclear reactor;generating an initial set of fuel design parameter values utilizing atleast one design variable of each of the set of regions; calculating atleast one reactor core parameter distribution of the simulated BOC coreutilizing the generated initial set of fuel design parameter valuesassociated with the set of regions located at the initial set ofpositions of the simulated BOC core; and generating a loadingdistribution by performing at least one perturbation process on the setof regions of the simulated BOC core in order to determine a subsequentset of positions for the set of regions within the simulated BOC core.

In another aspect, a method includes, but is not limited to, receivingat least one reactor core parameter distribution associated with a stateof a core of a reference nuclear reactor; generating an initial fuelloading distribution for a simulated BOC core of a nuclear reactor;selecting an initial set of positions associated within a set of regionswithin the simulated BOC core of the nuclear reactor; generating aninitial set of fuel design parameter values utilizing at least onedesign variable of each of the set of regions; calculating at least onereactor core parameter distribution of the simulated BOC core utilizingthe generated initial set of fuel design parameter values associatedwith the set of regions located at the initial set of positions of thesimulated BOC core; and generating a loading distribution by performingat least one perturbation process on the set of regions of the simulatedBOC core in order to determine a subsequent set of positions for the setof regions within the simulated BOC core; and arranging at least onefuel assembly of a core of a nuclear reactor according to the subsequentset of positions of the set of regions of the simulated BOC core.

In another aspect, a method includes, but is not limited to, determiningan initial loading distribution of a core of a nuclear reactor utilizinga BOC simulation process to generate a simulated BOC nuclear reactorcore; arranging at least one fuel assembly of the core of the nuclearreactor according to a set of simulated positions of a set of regions ofthe simulated BOC nuclear reactor core; operating the core of thenuclear reactor for a selected time interval; generating a measuredreactor core parameter distribution utilizing at least one measurementof at least one reactor core parameter at one or more locations withinthe core of the nuclear reactor; comparing the generated measuredreactor core parameter distribution to at least one reactor coreparameter distribution of a simulated operated nuclear reactor core; anddetermining an operational compliance state of the core of the nuclearreactor using the comparison between the generated measured reactor coreparameter distribution and the at least one reactor core parameterdistribution of the simulated operated nuclear reactor core.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

In one aspect, a non-transitory computer-readable medium includes, butis not limited to, program instructions executable to: receive at leastone reactor core parameter distribution associated with a state of acore of a reference nuclear reactor; generate an initial fuel loadingdistribution for a simulated BOC core of a nuclear reactor; select aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor; generate an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions; calculate at least one reactor coreparameter distribution of the simulated BOC core utilizing the generatedinitial set of fuel design parameter values associated with the set ofregions located at the initial set of positions of the simulated BOCcore; and generate a subsequent loading distribution by performing atleast one perturbation process on the set of regions of the simulatedBOC core in order to determine a subsequent set of positions for the setof regions within the simulated BOC core.

In another aspect, a non-transitory computer-readable medium includes,but is not limited to, program instructions executable to: receive atleast one reactor core parameter distribution associated with a state ofa core of a reference nuclear reactor; generate an initial fuel loadingdistribution for a simulated BOC core of a nuclear reactor; select aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor; generate an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions; calculate at least one reactor coreparameter distribution of the simulated BOC core utilizing the generatedinitial set of fuel design parameter values associated with the set ofregions located at the initial set of positions of the simulated BOCcore; and generate a subsequent loading distribution by performing atleast one perturbation process on the set of regions of the simulatedBOC core in order to determine a subsequent set of positions for the setof regions within the simulated BOC core; and arrange at least one fuelassembly of a core of a nuclear reactor according to the subsequent setof positions of the set of regions of the simulated BOC core.

In another aspect, a non-transitory computer-readable medium includes,but is not limited to, program instructions executable to: determine aninitial loading distribution of a core of a nuclear reactor utilizing aBOC simulation process to generate a simulated BOC nuclear reactor core;arrange at least one fuel assembly of the core of the nuclear reactoraccording to a set of simulated positions of a set of regions of thesimulated BOC nuclear reactor core; operate the core of the nuclearreactor for a selected time interval; generate a measured reactor coreparameter distribution utilizing at least one measurement of at leastone reactor core parameter at one or more locations within the core ofthe nuclear reactor; compare the generated measured reactor coreparameter distribution to at least one reactor core parameterdistribution of a simulated operated nuclear reactor core; and determinean operational compliance state of the core of the nuclear reactor usingthe comparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated core.

In another aspect, a system includes, but is not limited to, acontroller including one or more processors operable to execute programinstructions maintained on a non-transitory computer-readable medium,the program instructions configured to: receive at least one reactorcore parameter distribution associated with a state of a core of areference nuclear reactor; generate an initial fuel loading distributionfor a simulated BOC core of a nuclear reactor; select an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor, each of the initial set of positionscorresponding to one of the set of regions; generate an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the set of regions ofthe simulated BOC core of the nuclear reactor; calculate at least onereactor core parameter distribution of the simulated BOC core utilizingthe generated initial set of fuel design parameter values associatedwith the set of regions located at the initial set of positions of thesimulated BOC core; and generate a subsequent loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, thesubsequent set of positions defining the loading distribution for thesimulated BOC core, wherein the subsequent set of positions reduce thedifference between the at least one reactor core parameter distributionof the simulated BOC core and the received at least one reactor coreparameter distribution associated with a state of a core of a referencenuclear reactor below a selected tolerance level.

In another aspect, a system includes, but is not limited to, acontroller including one or more processors operable to execute programinstructions maintained on a non-transitory computer-readable medium,the program instructions configured to: receive at least one reactorcore parameter distribution associated with a state of a core of areference nuclear reactor; generate an initial fuel loading distributionfor a simulated BOC core of a nuclear reactor; select an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor, each of the initial set of positionscorresponding to one of the set of regions; generate an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the set of regions ofthe simulated BOC core of the nuclear reactor; calculate at least onereactor core parameter distribution of the simulated BOC core utilizingthe generated initial set of fuel design parameter values associatedwith the set of regions located at the initial set of positions of thesimulated BOC core; and generate a subsequent loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, thesubsequent set of positions defining the loading distribution for thesimulated BOC core, wherein the subsequent set of positions reduce thedifference between the at least one reactor core parameter distributionof the simulated BOC core and the received at least one reactor coreparameter distribution associated with a state of a core of a referencenuclear reactor below a selected tolerance level; and a nuclear reactor,the nuclear reactor including a nuclear reactor core including aplurality of fuel assemblies arrangeable according to the subsequentloading distribution determined by the controller.

In another aspect, a system includes, but is not limited to, a nuclearreactor including a nuclear reactor core, the nuclear reactor coreincluding a plurality of fuel assemblies; and a controller configuredto: determine an initial loading distribution of the nuclear reactorcore utilizing a BOC simulation process to generate a simulated BOCnuclear reactor core; generate a measured reactor core parameterdistribution utilizing at least one measurement of at least one reactorcore parameter at one or more locations within the core of the nuclearreactor, following operation of the nuclear reactor for a selected timeinterval; compare the generated measured reactor core parameterdistribution to at least one reactor core parameter distribution of asimulated operated nuclear reactor core generated utilizing at least theinitial loading distribution; and determine an operational compliancestate of the core of the nuclear reactor using the comparison betweenthe generated measured reactor core parameter distribution and the atleast one reactor core parameter distribution of the simulated operatednuclear reactor core, wherein the plurality of fuel assemblies of thenuclear reactor core are arrangeable according to a set of simulatedpositions of a set of regions of at least one of the simulated BOCnuclear reactor core and an additional simulated operated nuclearreactor core.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure.

The foregoing is a summary and thus may contain simplifications,generalizations, inclusions, and/or omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is NOT intended to be in any way limiting. Otheraspects, features, and advantages of the devices and/or processes and/orother subject matter described herein will become apparent in theteachings set forth herein.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1A is a block diagram view of a system for generating a simulatedloading distribution in a BOC nuclear reactor core, in accordance withan embodiment of the present invention;

FIG. 1B is a block diagram view of the programming modules implementableby the system for generating a simulated loading distribution in a BOCnuclear reactor core, in accordance with an embodiment of the presentinvention;

FIG. 1C is a block diagram view of the databases implementable by thesystem for generating a simulated loading distribution in a BOC nuclearreactor core, in accordance with an embodiment of the present invention;

FIG. 1D is a block diagram view of types of nuclear reactor coreparameter distributions, in accordance with an embodiment of the presentinvention;

FIG. 1E is a cross-sectional view of a nuclear reactor core formed frommultiple fuel assemblies, in accordance with an embodiment of thepresent invention;

FIG. 1F is an isometric view of a nuclear reactor core formed frommultiple fuel assemblies, in accordance with an embodiment of thepresent invention;

FIG. 1G is a cross-sectional view of a fuel assembly containing multiplefuel pins, in accordance with an embodiment of the present invention;

FIG. 1H is a block diagram view of types of nuclear reactor fuel of thesimulated BOC nuclear reactor core, in accordance with an embodiment ofthe present invention;

FIG. 1I is a cross-sectional view of a nuclear reactor core formed frommultiple fuel assemblies with the selected regions for executing thesimulation of the present invention depicted, in accordance with anembodiment of the present invention;

FIG. 1J is a cross-sectional view of a nuclear reactor core formed frommultiple fuel assemblies with a selected region for executing thesimulation of the present invention encompassing multiple fuelassemblies of the reactor core, in accordance with an embodiment of thepresent invention;

FIG. 1K is an isometric view of a fuel assembly with multiplesub-assembly simulation regions depicted, in accordance with anembodiment of the present invention;

FIG. 1L is a cross-sectional view of a nuclear reactor core formed frommultiple fuel assemblies depicting the use of multiple regions tocalculate one or more characteristics of a single region via statisticalaggregation;

FIG. 1M is a block diagram view of types of design variables, inaccordance with an embodiment of the present invention;

FIG. 1N is a block diagram view of types of nuclear fuel designparameters, in accordance with an embodiment of the present invention;

FIG. 1O is a block diagram view of types of nuclear reactor coreparameter distributions, in accordance with an embodiment of the presentinvention;

FIG. 1P is process flow diagram depicting a perturbation procedureexecutable by system for generating a simulated loading distribution ina BOC nuclear reactor core, in accordance with an embodiment of thepresent invention;

FIG. 2A is a block diagram view of a system for arranging one or morefuel assemblies in a nuclear reactor core, in accordance with anembodiment of the present invention;

FIG. 2B is a schematic view of a system for arranging one or more fuelassemblies in a nuclear reactor core, in accordance with an embodimentof the present invention;

FIG. 2C is a block diagram view of the programming modules implementableby the system for arranging one or more fuel assemblies in a nuclearreactor core, in accordance with an embodiment of the present invention;

FIG. 2D is a block diagram view of types of nuclear reactors for use inthe present invention, in accordance with an embodiment of the presentinvention;

FIG. 3A is a block diagram view of a system for determining a state ofoperation compliance of a nuclear reactor core, in accordance with anembodiment of the present invention;

FIG. 3B is a block diagram view of the programming modules implementableby the system for determining a state of operation compliance of anuclear reactor core, in accordance with an embodiment of the presentinvention;

FIG. 3C is a block diagram view of types of nuclear reactor coremeasurement systems suitable for use in the present invention, inaccordance with an embodiment of the present invention;

FIG. 3D is process flow diagram depicting an operation cycle of thesystem for determining a state of operation compliance of a nuclearreactor core, in accordance with an embodiment of the present invention.

FIG. 4A is a high-level flowchart of a method for generating a simulatedloading distribution in a BOC nuclear reactor core;

FIGS. 4B through 26 are high-level flowcharts depicting alternateimplementations of FIG. 4A.

FIG. 27A is a high-level flowchart of a method for arranging one or morefuel assemblies in a nuclear reactor core;

FIGS. 27B through 54 are high-level flowcharts depicting alternateimplementations of FIG. 27A.

FIG. 55 is a high-level flowchart of a method for determining a state ofoperation compliance of a nuclear reactor core;

FIGS. 56 through 68 are high-level flowcharts depicting alternateimplementations of FIG. 55.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

Referring generally to FIGS. 1A through 1P, a system 100 for generatinga simulated nuclear fuel loading distribution of a nuclear reactor coreis described in accordance with the present invention. It is recognizedherein that nuclear reactors, such as a breed-and-burn type nuclearreactor, experience a transitional period, which require reloading andigniter-savoring shuffling in order to maintain reactivity as thecomposition of the reactor core evolves from a beginning-of-life (BOL)state to an equilibrium- or near-equilibrium state. During thistransitional time, operators of the nuclear reactor are required toimplement a carefully scheduled and highly sensitive fuel shufflingroutine.

The present invention is directed to the determination of thedistribution of newly loaded nuclear fuel producing a reactor coreparameter distribution that deviates from a reference reactor coreparameter distribution associated with a reference nuclear reactor by amagnitude equal to or less than a selected tolerance value). In oneembodiment of the present invention, the system 100 may be implementedto determine an enrichment distribution of fresh or recycled nuclearfuel suitable for producing a reactor core parameter distribution thatdeviates from a parameter distribution (e.g., power density distributionor reactivity distribution) of an operated reference nuclear reactorcore (i.e., made up of at least partially burned nuclear fuel) in astate of equilibrium by a magnitude equal to or less than a selectedlevel of accuracy. As such, the present invention is capable ofproviding equilibrium-like benefits in a first generation reactor,thereby eliminating or at least reducing the need for time consumingtransition from a beginning-of-life state to an equilibrium state.

FIG. 1A illustrates a block diagram view of a loading distributiongeneration system 100, in accordance with one embodiment of the presentinvention. In one aspect of the present invention, the loadingdistribution generation system 100 may include a controller 102. Inanother aspect of the present invention, the controller 102 iscommunicatively coupled to a core parameter distribution source 104(e.g., core parameter distribution database maintained in memory). Inanother aspect of the present invention, the controller 102 isconfigured to receive one or more reactor core parameter distributions103 (e.g., power distribution) associated with a state (e.g.,equilibrium state) of a core of a nuclear reactor from the coreparameter distribution source 104. In an additional aspect of thepresent invention, the controller 102 is configured to generate aninitial fuel loading distribution for a simulated beginning-of-cycle(BOC) core of the nuclear reactor. In another aspect of the presentinvention, the controller 102 is configured to select an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor. In another aspect of the present invention, thecontroller 102 is configured to generate an initial set of fuel designparameter values utilizing at least one design variable of each of theset of regions. In another aspect of the present invention, thecontroller 102 is configured to calculate a reactor core parameterdistribution of the simulated BOC core utilizing the generated initialset of fuel design parameter values associated with the set of regionslocated at the initial set of positions of the simulated BOC core. Inanother aspect of the present invention, the controller 102 isconfigured to generate a loading distribution by performing one or moreperturbation processes on the set of regions of the simulated BOC corein order to determine a subsequent set of positions for the set ofregions within the simulated BOC core. In this regard, the subsequent,or final, set of positions act to converge the reactor core parameterdistribution of the simulated BOC core toward the reactor core parameterdistribution received from the reference reactor within a predeterminedtolerance level, even though the simulated BOC core is made up of anuclear fuel distribution different from the nuclear fuel distributionof the core of the reference reactor.

FIG. 1B illustrates a block diagram of one or more sets of programinstructions 105 maintained in memory 108 (as shown in FIG. 1A) andconfigured to carry out one or more steps described throughout thepresent disclosure. FIG. 1C illustrates a block diagram of a set ofdatabases 107 maintained in memory 108 (or any other known memory deviceknown in the art) and configured to store results of one or more stepsof the present invention. Each of these steps will be described infurther detail throughout the remainder of this disclosure.

In one embodiment of the present invention, the controller 102 mayinclude, but is not limited to, one or more computer processors 106configured to carry out one or more of the various steps describedthroughout the present disclosure. In this regard, the one or moreprocessors 106 may retrieve program instructions 105 maintained in thenon-transitory medium (e.g., memory 108 of controller 102) suitable forcausing the one or more processors 106 to carry out one or more of thevarious steps described throughout the present disclosure. In oneembodiment, the controller 102 may include any computational deviceknown in the art. The controller 102 may include, but is not limited to,a personal computer system, mainframe computer system, workstation,image computer, parallel processor, or any other computational deviceknown in the art. In general, the term “computational device” may bebroadly defined to encompass any device having data processingcapabilities. For example, a computational device may include, but isnot limited to, one or more processors suitable for executing computerprogram instructions from a non-transitory medium. The non-transitorymedium may include, but is not limited to, a read-only memory, a randomaccess memory, a magnetic or optical disk, a solid state memory, amagnetic tape or the like.

Referring again to FIG. 1A, in one embodiment of the present invention,the one or more processors 106 of the controller 102 are communicativelycoupled to the core parameter distribution source 104 and configured toreceive one or more reactor core parameter distributions 103 from thecore parameter distribution source 104. In one embodiment, the one ormore processors 106 of the controller 102 may receive a reactor coreparameter distribution for a core of a reference nuclear reactor in agiven state in the form of a database. In another embodiment, the one ormore processors 106 of the controller 102 may receive a reactor coreparameter distribution for a core of a nuclear reactor in a given statein the form of a data set representative of a map, such as, but notlimited to, a two-dimensional map or a three-dimensional map indicativeof the reactor core parameter as a function of position within the coreof the reference nuclear reactor.

In one embodiment, the core parameter distribution source 104 mayinclude, but is not limited to, one or more memory devices configured tostore and/or maintain one or more reactor core parameter distributions103 associated with a state of a core of a nuclear reactor. The coreparameter distribution source 104 may include any memory device known inthe art. In one embodiment, the core parameter distribution source 104includes a portable memory device suitable for storing one or morereactor core parameter distributions 103. For example, the coreparameter distribution source 104 may include, but is not limited to, aportable flash drive, an optical disc, a solid state drive, and thelike. In another embodiment, the core parameter distribution source 104includes a remote memory device or system suitable for storing one ormore reactor core parameter distributions 103. For example, the coreparameter distribution source 104 may include, but is not limited to, aremote server communicatively coupled to the controller 102 via a datanetwork (e.g., internet). By way of another example, the core parameterdistribution source 104 may include, but is not limited to, a localserver communicatively coupled to the controller 102 via a local datanetwork (e.g., intranet). In another embodiment, the core parameterdistribution source 104 may include, but is not limited to, the memorymedium 108 of the controller 102.

In one embodiment, the one or more reactor core parameter distributions103 may include a measured reactor core parameter distribution. Forinstance, a reactor core parameter distribution may be acquired bymeasuring the reactor core parameter distribution of an operatingnuclear reactor while in the desired state (e.g., equilibrium or nearequilibrium state, state approaching equilibrium, or state ofequilibrium onset). In another embodiment, the one or more reactor coreparameter distributions 103 may include a simulated reactor coreparameter distribution. For instance, a reactor core parameterdistribution may be acquired via computer simulation of a selectednuclear reactor (e.g., nuclear reactor loaded with “non-fresh” fuel)while in the desired state (e.g., equilibrium or near equilibrium state,state approaching equilibrium, or state of equilibrium onset).

In one embodiment, the one or more reactor core parameter distributions103 include a reactor core parameter distribution of an equilibriumstate of a nuclear reactor. For example, one or more reactor coreparameter distributions 103 associated with an equilibrium state of acore of a reference nuclear reactor may be maintained in the coreparameter distribution source 104. Then, the one or more stored reactorcore parameter distributions associated with an equilibrium state of acore of a nuclear reactor may be transmitted from the core parameterdistribution source 104 to the one or more processors 106 of thecontroller 102.

In another embodiment, the one or more reactor core parameterdistributions 103 include a reactor core parameter distribution of anequilibrium-approaching state of a nuclear reactor. For example, one ormore reactor core parameter distributions 103 associated with anequilibrium-approaching state of a core of a reference nuclear reactormay be maintained in the core parameter distribution source 104. Then,the one or more stored reactor core parameter distributions 103associated with an equilibrium-approaching state of a core of a nuclearreactor may be transmitted from the core parameter distribution source104 to the one or more processors 106 of the controller 102.

In another embodiment, the one or more reactor core parameterdistributions 103 include a reactor core parameter distribution of anequilibrium-onset state of a nuclear reactor. For example, one or morereactor core parameter distributions 103 associated with anequilibrium-onset state of a core of a reference nuclear reactor may bemaintained in the core parameter distribution source 104. Then, the oneor more stored reactor core parameter distributions 103 associated withan equilibrium onset state of a core of a nuclear reactor may betransmitted from the core parameter distribution source 104 to the oneor more processors 106 of the controller 102.

FIG. 1D illustrates a block diagram of types of reactor core parameterdistributions 103 received from the core parameter distribution source104, in accordance with one or more embodiments of the presentinvention. The one or more reactor core parameter distributions 103received from the core parameter distribution source 104 may include anyreactor core parameter distribution known in the art. In one embodiment,the one or more reactor core parameter distributions 103 received fromthe core parameter distribution source 104 include, but are not limitedto, a power density distribution 109 or a rate of change of a powerdensity distribution 110 of the core of a nuclear reactor. For example,the power distribution 109 (or distribution of rate of change of powerdensity 110) associated with a state of a core of a reference nuclearreactor may be stored in the core parameter distribution source 104.Then, the stored reactor core power density distribution 109 (ordistribution of rate of change of power density 110) associated with astate of the core of the reference nuclear reactor may be transmittedfrom the core parameter distribution source 104 to the one or moreprocessors 106 of the controller 102.

In another embodiment, the one or more core parameter distributionsreceived from the core parameter distribution source 104 include, butare not limited to, a reactivity distribution 111 or a rate of change ofreactivity distribution 112 of the core of a nuclear reactor. Forexample, the reactivity distribution 111 (or distribution of rate ofchange of reactivity 112) associated with a state of a core of areference nuclear reactor may be stored in the core parameterdistribution source 104. Then, the stored reactor core reactivitydistribution 111 (or distribution of rate of change of reactivity 112)associated with a state of the core of the reference nuclear reactor maybe transmitted from the core parameter distribution source 104 to theone or more processors 106 of the controller 102.

The one or more reactor core parameter distributions 103 may beassociated with a state of a core of any nuclear reactor known in theart. In some embodiments, the one or more reactor core parameterdistributions 103 may be associated with a state of a core of at leastone of a thermal nuclear reactor (e.g., light water reactor), a fastnuclear reactor, a breed-and-burn nuclear reactor and a traveling wavernuclear reactor. For example, one or more reactor core parameterdistributions 103 associated with a state of a core of a referencethermal nuclear reactor may be stored in the core parameter distributionsource 104. Then, the stored parameter distribution associated with astate of the core of the reference thermal nuclear reactor may betransmitted from the core parameter distribution source 104 to the oneor more processors 106 of the controller 102. By way of another example,one or more reactor core parameter distributions associated with a stateof a core of a reference fast nuclear reactor may be stored in the coreparameter distribution source 104. Then, the stored parameterdistribution associated with a state of the core of the reference fastnuclear reactor may be transmitted from the core parameter distributionsource 104 to the one or more processors 106 of the controller 102. Byway of another example, one or more reactor core parameter distributionsassociated with a state of a core of a reference breed-and-burn nuclearreactor may be stored in the core parameter distribution source 104.Then, the stored parameter distribution associated with a state of thecore of the reference breed-and-burn nuclear reactor may be transmittedfrom the core parameter distribution source 104 to the one or moreprocessors 106 of the controller 102. By way of another example, one ormore reactor core parameter distributions associated with a state of acore of a reference traveling wave nuclear reactor may be stored in thecore parameter distribution source 104. Then, the stored parameterdistribution associated with a state of the core of the referencetraveling wave nuclear reactor may be transmitted from the coreparameter distribution source 104 to the one or more processors 106 ofthe controller 102.

In another embodiment, the one or more reactor core parameterdistributions 103 may be associated with a state of a core of a nuclearreactor having one or more fuel assemblies. For example, one or morereactor core parameter distributions associated with a state of a coreof a reference nuclear reactor having one or more fuel assemblies may bestored in the core parameter distribution source 104. Then, the storedparameter distribution associated with a state of the core of thereference nuclear reactor having one or more fuel assemblies may betransmitted from the core parameter distribution source 104 to the oneor more processors 106 of the controller 102.

In a further embodiment, the one or more reactor core parameterdistributions 103 may be associated with a state of a core of a nuclearreactor having one or more fuel assemblies with one or more fuel pins.For example, one or more reactor core parameter distributions associatedwith a state of a core of a reference nuclear reactor having one or morefuel assemblies with one or more fuel pins may be stored in the coreparameter distribution source 104. Then, the stored parameterdistribution associated with a state of the core of the referencenuclear reactor having one or more fuel assemblies with one or more fuelpins may be transmitted from the core parameter distribution source 104to the one or more processors 106 of the controller 102. Those skilledin the art will recognize that a given fuel assembly may include anumber of fuel pins assembled into a predefined array structure. It isfurther noted that the chosen pin/fuel arrangement within a fuelassembly may be chosen in an effort to optimize neutronic performance.The arrangement of fuel pins in a hexagonal fuel assembly of a breederreactor is generally described in Alan E. Waltar and Albert B. Reynolds,Fast Breeder Reactors, 1st ed, Pergamon Press Inc., 1981, p. 119, whichis incorporated herein by reference in the entirety. It is recognizedherein that a core parameter distribution having any known pinarrangement within a given fuel assembly structure of a nuclear reactorcore is suitable for implementation in the present invention.

It is noted herein that the one or more stored reactor core parameterdistributions 103 may be associated with a state of a core of areference nuclear reactor including any fissile or fissionable materialknown in the art. In one embodiment, the one or more reactor coreparameter distributions 103 may be associated with a state of a core ofa nuclear reactor including plutonium. For example, one or more reactorcore parameter distributions associated with a state of aplutonium-containing-core of a reference nuclear reactor may be storedin the core parameter distribution source 104. Then, the storedparameter distribution associated with a state of theplutonium-containing-core of the reference nuclear reactor may betransmitted from the core parameter distribution source 104 to the oneor more processors 106 of the controller 102. In another embodiment, theone or more reactor core parameter distributions 103 may be associatedwith a state of a core of a nuclear reactor including uranium. Forexample, one or more reactor core parameter distributions associatedwith a state of a uranium-containing-core of a reference nuclear reactormay be stored in the core parameter distribution source 104. Then, thestored parameter distribution associated with a state of theuranium-containing-core of the reference nuclear reactor may betransmitted from the core parameter distribution source 104 to the oneor more processors 106 of the controller 102.

Referring again to FIGS. 1A and 1B, in one embodiment of the presentinvention, the one or more processors 106 of controller 102 areconfigured to generate an initial fuel loading distribution for asimulated BOC core of a nuclear reactor. It is noted herein that theinitial fuel loading distribution (or any fuel loading distributiondescribed herein) is representative of the spatial arrangement of thevarious components of nuclear fuel within a nuclear reactor core (e.g.,simulated core or real core). In this regard, a given nuclear fuelloading distribution of the present invention (e.g., initial fuelloading distribution) may consist of a database or map (e.g.,two-dimensional or three-dimensional map) indicative of the distributionof component materials of the nuclear fuel as a function of positionwithin the core of the nuclear reactor.

For example, as shown in FIG. 1B, the program instructions 105 of memory108 may include an initial nuclear fuel loading distribution generator130 configured to cause the one or more processors 106 of controller 102to generate an initial fuel loading distribution for a simulated BOCcore of a nuclear reactor. In a further embodiment, as shown in FIG. 1C,the controller 102 may store the generated initial fuel loadingdistribution 139 in one or more databases 107 maintained in memory 108or any other known memory device known in the art.

In one embodiment, based on the received one or more reactor coreparameter distributions 103 from the core parameter distribution source104, the one or more processors 106 of the controller 102 may generatean initial nuclear fuel loading distribution for a simulated BOC core ofa nuclear reactor. For instance, the one or more processors 106 maycompare historical data stored in the memory 108 of the controller 102(or memory from a remote data source) to the received one or morereactor core parameter distributions 103 from the core parameterdistribution source 104 to generate an initial nuclear fuel loadingdistribution for the simulated BOC core of a nuclear reactor. Then, theone or more processors 106 may transmit the generated initial nuclearfuel loading distribution 139 to one or more databases 107 in memory 108for storage.

In another embodiment, an initial fuel loading distribution for asimulated BOC core of a nuclear reactor may be selected or entered intothe controller 102 via user input. For example, a user input device 118of a user interface 114 may be used by a user to input an initial fuelloading distribution for a simulated BOC core of a nuclear reactor intothe controller 102 (e.g., input distribution into memory 108). By way ofanother example, the one or more processors 106 of the controller 102may present a set of initial fuel loading distribution options to theuser via the display 116 of the user interface 114. Then, the user mayselect one or more of the sets of initial fuel loading distributionoptions displayed on display 114. In a further embodiment, the initialfuel loading distribution options may be derived based on the one ormore reactor core parameter distributions 103 received from the coreparameter distribution source 104.

In another embodiment, the controller 102 is configured to randomlygenerate an initial fuel loading distribution for a simulated BOC coreof a nuclear reactor. For example, based on the received one or morereactor core parameter distributions 103 from the core parameterdistribution source 104, the one or more processors 106 of thecontroller 102 may randomly generate an initial nuclear fuel loadingdistribution for a simulated BOC core of a nuclear reactor.

FIGS. 1E-1F illustrate a graphical representation of a simulated nuclearreactor core 120, in accordance with one embodiment of the presentinvention. In one embodiment, an initial fuel loading distribution maybe generated by the controller 102 for the simulated BOC core 120 of thenuclear reactor including, but not limited to, a plurality of simulatedfuel assemblies 124, as shown in FIGS. 1E and 1F. In a furtherembodiment, based on the received one or more reactor core parameterdistributions 103 from the core parameter distribution source 104, theone or more processors 106 of the controller 102 may generate an initialnuclear fuel loading distribution for a simulated BOC core 120 of anuclear reactor having a plurality of fuel assemblies 124. It is notedherein that the simulated BOC core 120 of the present invention may takeon any number of forms. FIGS. 1E and 1F depict a core 120 equipped withmultiple hexagonoid-shape fuel assemblies 124 arranged in a hexagonalarray. It is further noted that the depicted arrangements in FIGS. 1Eand 1F is not limiting and is provided merely for illustration. It isnoted that the simulated core 120 of the present invention may includealternative fuel assembly structures, such as, but not limited to,cylinders, parallelepipeds, triangular prisms, conical structures,helical structures and the like. Further, the array structure of thefuel assemblies of the simulated core 120 of the present invention mayinclude alternative array structures, such as, but not limited to, arectangular array, a square array, a cylindrical close packed array, aconcentric ring array and the like.

As shown in FIG. 1G, in a further embodiment, one or more of thesimulated fuel assemblies 124 of the BOC core 120 may include, but arenot limited to, a plurality of fuel pins 125. In one embodiment, basedon the received one or more reactor core parameter distributions 103from the core parameter distribution source 104, the one or moreprocessors 106 of the controller 102 may generate an initial nuclearfuel loading distribution for a simulated BOC core 120 of a nuclearreactor having a plurality of fuel assemblies 124, each equipped withmultiple fuel pins 125.

It is noted herein that the structure and arrangement of the fuel pinswithin each fuel assembly 124 of the simulated core 120 may take on anyform known in the art. For example, as shown in FIG. 1G, the fuel pinsmay be cylindrically shaped and arranged within a close packed hexagonalarray within the fuel assembly 124. In other embodiments, although notshown, the simulated fuel pins of the core may have a hexagonoid shape,a parallelepiped shape, a triangular prism shape, a helical shape, aconical shape and the like. In another embodiment, although not shown,the simulated fuel pins of the core may be arranged in a rectangulararray, a square array, a concentric ring array and the like.

In another embodiment, each of the plurality of fuel pins 125 in asimulated fuel assembly 124 of the simulated BOC core 120 may include aselected nuclear fuel. In this regard, the initial fuel loadingdistribution may be generated by the controller 102 for a simulated BOCcore including any nuclear fuel known in the art. In one embodiment, thecontroller 102 may build up the simulated BOC core by selecting thenuclear fuel composition for each pin of each fuel assembly of the BOCcore, resulting in a full core-wide nuclear fuel distribution. Forexample, as shown in FIG. 1H, a portion of the nuclear fuel 126 of thesimulated BOC core may include, but not limited to, recycled nuclearfuel 127, unburned nuclear fuel 128, or enriched nuclear fuel 129.

For example, in response to the received one or more reactor coredistributions 103 received from the core parameter distribution source104, the one or more processors 106 are configured to generate aninitial fuel loading distribution for a simulated BOC core of a nuclearreactor including recycled nuclear fuel 127. For instance, one or morefuel pins 125 of one or more fuel assemblies 124 of the simulated core120 may contain a selected amount and type of recycled nuclear fuel 127.

By way of another example, in response to the received one or morereactor core parameter distributions 103 from the core parameterdistribution source 104, the one or more processors 106 are configuredto generate an initial fuel loading distribution for a simulated BOCcore of a nuclear reactor including unburned nuclear fuel 128. Forinstance, one or more fuel pins 125 of one or more fuel assemblies 124of the simulated core 120 may contain a selected amount and type ofunburned nuclear fuel 128.

By way of another example, in response to the received one or morereactor core parameter distributions 103 from the core parameterdistribution source 104, the one or more processors 106 are configuredto generate an initial fuel loading distribution for a simulated BOCcore of a nuclear reactor including enriched nuclear fuel 129. Forinstance, one or more fuel pins 125 of one or more fuel assemblies 124of the simulated core 120 may contain a selected amount and type ofenriched nuclear fuel 129. It is noted herein that the simulated BOCnuclear reactor core may include any enriched nuclear reactor fuel knownin the art. For instance, the enriched nuclear fuel may include, but isnot limited to, enriched uranium fuel.

In another embodiment, the simulated BOC core of the nuclear reactor mayinclude, but is not limited to, a BOL core of the nuclear reactor. Assuch, the generated initial fuel loading distribution for the simulatedBOC core of the nuclear reactor may include, but is not limited to, aninitial fuel loading distribution for a simulated BOL core of thenuclear reactor. For example, the one or more processors 106 of thecontroller 102 may be configured to generate an initial fuel loadingdistribution for a simulated BOL core of a nuclear reactor. Forinstance, based on the received one or more reactor core parameterdistributions 103 from the core parameter distribution source 104, theone or more processors 106 of the controller 102 may generate an initialnuclear fuel loading distribution for a simulated BOL core of a nuclearreactor.

Referring again to FIGS. 1A-1C, in one embodiment of the presentinvention, the one or more processors 106 of the controller 102 areconfigured to select an initial set of positions associated with each ofa set of regions within the simulated BOC core 120 of the nuclearreactor. For example, as shown in FIG. 1B, the program instructions 105maintained in memory 108 may include an initial position selectoralgorithm 132 configured to cause the one or more processors 106 ofcontroller 102 to select an initial set of positions associated witheach of a set of regions within the simulated BOC core 120 of thenuclear reactor. In one embodiment, the one or more processors 106 ofthe controller 102 may transmit the initial set of selected positions140 (e.g., x, y, z positions; R, θ, φ positions and the like) to one ormore databases 107 of memory 108 for storage and later use.

FIGS. 1I-1K illustrate a graphical representation of a simulated BOCcore 120 and a set of regions 122 selected by one or more processors 106of the controller 102, in accordance with one embodiment of the presentinvention. In one embodiment, as shown in FIG. 1I, each region 122 maycorrespond with a single fuel assembly 124 of the BOC core 120. In thisregard, the one or more processors 106 of the controller 102 areconfigured to select an initial set of positions 140, whereby each ofthe set of selected initial positions 140 corresponds with the position(e.g., relative position) of the fuel assembly 124 of eachsingle-assembly encompassing region 122.

In another embodiment, as shown in FIG. 1J, each region 122 maycorrespond with two or more fuel assemblies 124 of the simulated BOCcore 120. For example, as shown in FIG. 1J, the surface of region 122may encompass fuel assemblies 124 a, 124 b and 124 c. In this regard,the one or more processors 106 of the controller 102 are configured toselect an initial set of positions 140 corresponding to two or more fuelassemblies 124 a-c contained within each of a set of regions 122 withinthe simulated BOC core of the nuclear reactor. It is noted herein thatwhile region 122 is depicted as encompassing three fuel assemblies 124in FIG. 1J, this should not be interpreted as a limitation. It isrecognized herein that each region 122 may encompass any suitable numberof fuel assemblies 124.

In another embodiment, as shown in FIG. 1K, each region 122 maycorrespond with a portion of a single assembly 124. For example, thesurface of each region 122 may encompass a single portion of a singlefuel assembly 124. For instance, as shown in FIG. 1K, in the case of ahexagonoid shaped fuel assembly 124, multiple “flat” hexagonoid shapedregions 122 a-122 g may each encompass different portions of the fuelassembly 124. While it is recognized herein that the positions of thesub-assembly regions 122 a-122 g are relatively fixed with respect toone another as the fuel assembly shape remains fixed (although expansionand warping caused by thermodynamic factors is anticipated), thesub-assembly regions 122 a-122 g may be utilized in the subsequentcalculation and modeling of features (e.g., calculation of fuel designparameters and etc.) of the simulated core 120 of the present inventionas described further herein. Further, it is recognized herein that incases where the fuel assemblies 124 have a substantially large axialdimension, such as the hexagonoid fuel assemblies in FIG. 1K, the use ofstacked sub-assembly regions 122 a-122 g allows for refinement in themodeling of reactor core 120 features along the axial direction. It isfurther noted that the particular shape and arrangement of thesub-assembly regions 122 a-122 g as depicted in FIG. 1K is not limitingand is provided merely for illustration.

For example, the sub-assembly regions 122 a-g may include, but are notlimited to, regions that are coextensive with one or more fuel pinscontained with one or more fuel assemblies 124. For instance, althoughnot shown in FIGS. 1I-1K, each region may encompass multiple fuel pinsof a given fuel assembly, whereby each of the set of selected initialpositions corresponds with each multi-pin encompassing region. In thisregard, the one or more processors 106 of the controller 102 areconfigured to select an initial set of positions 140 corresponding to aset of nuclear fuel pins contained within each of a set of regionswithin the simulated BOC core of the nuclear reactor. In this regard,each sub-assembly region encompassing a multiple pins of a given fuelassembly may be utilized in the subsequent calculation and modeling offeatures (e.g., calculation of fuel design parameters and etc.). Inanother instance, although not shown in FIGS. 1I-1K, each region mayencompass a single fuel pin, whereby each of the set of selected initialpositions corresponds with a group of single-pin encompassing regions.In this regard, each sub-assembly region encompassing a single pin of agiven fuel assembly may be utilized in the subsequent calculation andmodeling of features.

In another embodiment of the present invention, each of the set ofregions 122 includes, but is not limited to, a three-dimensional regionhaving a selected volume. In this regard, the one or more processors 106of the controller 102 are configured to select an initial set ofpositions 140 associated with a set of regions 122 defined by a threedimensional volume of selected size within the simulated BOC core 120 ofthe nuclear reactor. For example, the one or more processors 106 maydefine the size of the selected volume of each region based on apreprogrammed set of criteria. For instance, the selected volume of theconstituent regions within the simulated BOC core 120 may depend on avariety of factors including, but not limited to, the volume of thereactor core, the number of fuel assemblies and fuel pins within thereactor core, the speed required of the simulation and the like. By wayof another example, the one or more processors 106 may select the volumeof each region based on a user selection received via the user interfacedevice 118 of the user interface 114.

In another embodiment of the present invention, each of the set ofregions includes, but is not limited to, a three-dimensional regionhaving a selected shape. In this regard, the one or more processors 106of the controller 102 may select an initial set of positions 140associated with a set of regions within the simulated BOC core of thenuclear reactor, with each region being defined by a three dimensionalvolume having a selected shape. For example, as shown in FIG. 1I, theselected shape may include a hexagonoid. Further, as shown in FIG. 1I,the selected shape of the region 122 may outline a singlehexagonoid-shaped fuel assembly or multiple hexagonoid-shaped fuelassemblies, as shown in FIGS. 1I and 1J respectively. While the shape ofthe selected regions and fuel assemblies have been illustrated as havinga hexagonoid shape in FIGS. 1I and 1J, this should not be interpreted asa limitation of the present invention. The selected shape of the volumeof one or more of the set of regions (and the shape of the fuelassemblies) may include any known three dimensional geometric shape. Forexample, the shape of the volume may include, but is not limited to, acylinder, a parallelepiped (e.g., cuboid), a hexagonoid, an ellipsoid, asphere, a disc, a ring and the like. It is furthered note that there isno requirement that the selected regions take on the same general shapeas the fuel assemblies or fuel assembly ensembles of the BOC core. Inanother embodiment, the one or more processors 106 may define the shapeof the selected volume of each region based on a preprogrammed set ofcriteria. In another embodiment, the one or more processors 106 mayselect the shape of each volume of each region based on a user selectionreceived via the user interface device 118 of the user interface 114.

In another embodiment of the present invention, the number of regionsincluded in the set of regions within the simulated BOC nuclear reactorcore 120 is selectable. For example, the one or more processors 106 ofthe controller 102 are configured to select an initial set of positionsassociated with a set of regions consisting of a selected number ofregions within the simulated BOC core 120 of the nuclear reactor.Further, the one or more processors 106 may select the number of regionsbased on a preprogrammed set of criteria. Further, the one or moreprocessors 106 may select the number or regions based on a userselection received via the user interface device 118 of the userinterface 114.

Referring again to FIGS. 1A-1C, in one embodiment of the presentinvention, the one or more processors 106 of controller 102 areconfigured to generate an initial set of fuel design parameter valuesbased one or more design variables. In this regard, the one or moreprocessors 106 of controller 102 may generate a fuel design parametervalue for the simulated nuclear fuel within a given region 122 based onone or design variables (e.g., thermodynamic variable value, neutronicparameter value, and the like) associated with the simulated nuclearfuel within the given region 122. For example, as shown in FIG. 1B, theprogram instructions 105 maintained in memory 108 may include an initialfuel design parameter generator algorithm 134 configured to cause theone or more processors 106 of controller 102 to generate an initial setof fuel design parameter values based on or more design variables. In afurther embodiment, the one or more processors 106 of the controller 102may transmit the generated initial set of fuel design parameters 141 toone or more databases 107 of memory 108 for storage and later use.

In one embodiment, as graphically depicted in FIG. 1I, the one or moreprocessors 106 of controller 102 may generate an initial fuel designparameter value 141 for a first region 122 utilizing one or more designvariables associated with the nuclear fuel encompassed by the firstregion 122. In this regard, the one or more processors 106 of controller102 may build up a set of initial fuel design parameter values 141 byiteratively repeating this process for each region 122 in the simulatedBOC core 120.

In another embodiment, the one or more processors 106 of controller 102are configured to generate an initial fuel design parameter value 141for each region 122 utilizing one or more design variables for eachregion adjacent to a given region 122. As shown in FIG. 1L, the one ormore processors 106 of controller 102 may generate an initial fueldesign parameter value 141 for region 122 utilizing one or more designvariables for the region 122 and the regions 123 a-123 f surroundingregion 122. For example, the one or more processors 106 of controller102 may generate an initial fuel design parameter value 141 for region122 utilizing a statistical characteristic of one or more designvariables for the regions 123 a-123 f. For instance, the one or moreprocessors 106 of controller 102 may generate an initial fuel designparameter value 141 for region 122 utilizing an average value, a medianvalue, a maximum value, a minimum value or the like of the one or moredesign variables for the regions 123 a-123 f. In one example, the one ormore processors 106 of controller 102 may generate an initial fueldesign parameter value 141 for region 122 utilizing an average of theone or more design variable values for the regions 123 a-123 f. Inanother example, the one or more processors 106 of controller 102 maygenerate an initial fuel design parameter value 141 for region 122utilizing a statistical median of the one or more design variable valuesfor the regions 123 a-123 f. It is noted herein that any statisticalaggregation or selection of the one or more design variable values ofregions 122 and/or 123 a-123 f may be used to generate an initial fueldesign parameter value 141 for region 122. Further, the one or moreprocessors 106 of controller 102 may build up the set of initial fueldesign parameter values 141 by iteratively repeating this process foreach region in the simulated BOC core 120. While only one region 122 hasbeen depicted for calculation in FIG. 1L, it is noted that the set ofinitial fuel design parameter values 141 may be generated by repeatingthis process for each defined region 122 in the simulated BOC core 120.

In another embodiment, the one or more design variables may be utilizedat the pin-level (e.g., pins 125 of FIG. 1G) to generate an initial setof fuel design parameter values. In this regard, the one or moreprocessors 106 of controller 102 may generate an initial set of nuclearfuel design parameters based on one or more design variables associatedwith the nuclear fuel contained within each of the set of pins withineach of the set of regions 122. In a further embodiment, each of theinitial set of fuel design parameter values generated by the one or moreprocessors 106 of controller 102 is associated with one of the set ofregions 122 of the simulated BOC core 120 of the nuclear reactor. Inanother embodiment, each of the initial set of fuel design parametervalues generated by the one or more processors 106 of controller 102 isassociated with one of the pins of contained within one of the set ofregions 122 of the simulated BOC core 120 of the nuclear reactor.

FIG. 1M illustrates a block diagram of the types of design variables 144suitable for use by the controller 102 to generate the initial set offuel design parameter values, in accordance with one or more embodimentsof the present invention. In one embodiment, the initial set of fueldesign parameter values 141 generated by controller 102 may be based onone or more thermodynamic variables 145 associated with each of the setof regions 122. In this regard, the initial set of fuel design parametervalues may be based on a value of one or more thermodynamic variables145 for each region of the set of regions. For example, the one or moreprocessors 106 of the controller 102 may be configured to generate aninitial set of fuel design parameter values using a value of athermodynamic variable 145 for each of the set of regions 122 within thesimulated BOC core 120 of the nuclear reactor.

In another embodiment, the initial set of fuel design parameter values141 generated by controller 102 may be based on one or morethermodynamic variables 145 associated with each region adjacent to thegiven region in question. In this regard, each initial fuel designparameter value of a given region of the initial set of fuel designparameter values may be based on a value of one or more thermodynamicvariables for each region adjacent to the given region. For example, theone or more processors 106 of the controller 102 may be configured togenerate an initial fuel design parameter value for each region 122using a value of a thermodynamic variable 145 for region 122 and regions123 a-123 f adjacent to region 122 within the simulated BOC 120 core ofthe nuclear reactor.

It is noted herein that the one or more thermodynamic variables used togenerate the initial set of fuel design parameter values may include anythermodynamic variable known in the art. For example, the thermodynamicvariable may include, but is not limited to, the temperature 146 (e.g.,median temperature, average temperature, maximum temperature, minimumtemperature and the like) of each of the set of regions. By way ofanother example, the thermodynamic variable used to generate the initialset of fuel design parameter values may include, but is not limited to,the pressure 147 (e.g., median pressure, average pressure, maximumpressure, minimum pressure and the like) of each of the set of regions.

In another embodiment of the present invention, the initial set of fueldesign parameter values generated by controller 102 may be based on oneor more neutronic parameters 148 associated with each of the set ofregions. In this regard, the initial set of fuel design parameter valuesmay be based on a value of one or more neutronic parameters 148 for eachregion of the set of regions 122. For example, the one or moreprocessors 106 of the controller 102 may be configured to generate aninitial set of fuel design parameter values using a value of a neutronicparameter 148 for each of the set of regions 122 within the simulatedBOC core 120 of the nuclear reactor.

In another embodiment, the initial set of fuel design parameter values141 generated by controller 102 may be based on one or more neutronicparameters associated with a given region and each region adjacent tothe given region in question. In this regard, each initial fuel designparameter value 141 of a given region 122 of the initial set of fueldesign parameter values may be based on a value of one or more neutronicparameters 148 of the given region 122 and regions 123 a-123 f adjacentto the given region 122. For example, the one or more processors 106 ofthe controller 102 may be configured to generate an initial fuel designparameter value for each region 122 using a value of a neutronicparameter for region 122 and the regions 123 a-123 f adjacent to region122 within the simulated BOC 120 core of the nuclear reactor.

It is noted herein that the one or more neutronic parameter used togenerate the initial set of fuel design parameter values may include anyneutronic parameter known in the art. For example, the neutronicparameter may include, but is not limited to, a k-infinity value 149. Byway of another example, the neutronic parameter used to generate theinitial set of fuel design parameter values may include, but is notlimited to, neutron flux 150 of each of the set of regions. By way ofanother example, the neutronic parameter used to generate the initialset of fuel design parameter values may include, but is not limited to,neutron production rate 151 of each of the set of regions. By way ofanother example, the neutronic parameter used to generate the initialset of fuel design parameter values may include, but is not limited to,neutron absorption rate 152 of the each of the set of regions.

FIG. 1N illustrates a block diagram of the types of fuel designparameters 153 generated by the controller 102, in accordance with oneor more embodiments of the present invention. The initial fuel designparameters 141 generated by the controller 102 may include any fueldesign parameter suitable for implementation in the present invention.In one embodiment, the initial set of fuel design parameter values 141generated by controller 102 may include, but is not limited to, a set ofnuclear fuel enrichment values 154. For example, the one or moreprocessors 106 of controller 102 may generate an initial set of nuclearfuel enrichment values 154 associated with the set of regions located atthe initial set of positions in the simulated BOC core 120 using the oneor more design variables of each of the set of regions.

In another embodiment, the set of fuel design parameters generated bycontroller 102 may include, but is not limited to, a set of fuel pindimension values 155. For example, the one or more processors 106 ofcontroller 102 may generate an initial set of fuel pin dimension values155 associated with the fuel pins encompassed by each of the set ofregions located at the initial set of positions in the simulated BOCcore using the one or more design variables of each of the set ofregions.

The set of nuclear fuel pin dimension values 155 may include any nuclearfuel pin dimension value known in the art. For example, the set ofnuclear fuel pin dimension values 155 may include a fuel pinconfiguration value 156 (e.g., pin pitch value, number of pins and thelike) based on a configuration of multiple fuel pins in a single fuelassembly or multiple fuel assemblies. By way of another example, the setof nuclear fuel pin dimension values may include a fuel pin geometryvalue 157 (e.g., pin diameter value, pin shape and the like) based on aspatial feature of a representative fuel pin of multiple fuel pins in asingle fuel assembly or multiple fuel assemblies. By way of anotherexample, the set of nuclear fuel pin dimension values 155 may include afuel pin composition value 158 (e.g., ratio of fertile material tofissile material in one or more pins of one or more fuel assemblies)based on the chemical composition of the nuclear fuel contained withinthe multiple fuel pins in a single fuel assembly or a multiple fuelassembly.

In one embodiment, the set of nuclear fuel pin dimension values 155 mayinclude, but is not limited to, a pin pitch value. For instance, a pinpitch value may include the pin pitch value of a group of pins withinone or more fuel assemblies of the nuclear reactor core. In this regard,the pin pitch value may be defined by the pin pitch throughout one ormore fuel assemblies, each containing multiples fuel pins, of a nuclearreactor core. For example, the one or more processors 106 of controller102 may generate an initial set of pin pitch values associated with theset of regions located at the initial set of positions in the simulatedBOC core using the one or more design variables of each of the set ofregions. In another embodiment, the set of nuclear fuel pin dimensionvalues may include, but is not limited to, the number of fuel pinswithin the BOC core 120.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, a pin diameter value. For example, apin diameter value may include the pin diameter value of a group of pinswithin the nuclear reactor core. In this regard, the pin diameter valuemay be defined by the pin diameter (e.g., average pin diameter, mean pindiameter, and the like) of the fuel pins contained within one or morefuel assemblies of a nuclear reactor core. For example, the one or moreprocessors 106 of controller 102 may generate an initial set of pindiameter values associated with the set of regions located at theinitial set of positions in the simulated BOC core using the one or moredesign variables of each of the set of regions. It is noted herein thatthe size of the coolant channels within a given fuel assembly of anuclear reactor core is generally defined by the pin pitch and the pindiameter of the set of pins contained within the given fuel assembly.

In another embodiment, the set of nuclear fuel pin dimension 155 valuesmay include, but is not limited to, a pin-size value. For instance, apin-size value may include, but is not limited to, the pin length, pinradius (or pin width) or pin volume of the fuel pins within one or morefuel assemblies of the nuclear reactor core. For example, the one ormore processors 106 of controller 102 may generate an initial set of pinsize values associated with the set of regions 122 located at theinitial set of positions 140 in the simulated BOC core 120 using the oneor more design variables of each of the set of regions.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, a pin shape. For example, the one ormore processors 106 of controller 102 may generate an initial set of pinshapes associated with the set of regions 122 located at the initial setof positions 140 in the simulated BOC core 120 using the one or moredesign variables of each of the set of regions. In some embodiments, asdescribed previously herein, the pin shape may include any geometricshape known in the art, such as, but not limited to, a hexagonoid, acylinder, a parallelepiped, a triangular prism, a conical shape, ahelical shape and the like. In other embodiments, the pin shape mayinclude an irregular shape. For instance, the pin shape may include awarped or distorted regular geometric shape.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, a pin position within the BOC core120. For example, the one or more processors 106 of controller 102 maygenerate an initial set of positions 140 of multiple fuel pinsencompassed by the each of the set of regions 122 located at the initialset of positions in the simulated BOC core 120 using the one or moredesign variables of each of the set of regions.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, a fuel smear density value. Forexample, a fuel smear density value may include the nuclear fuel smeardensity value associated with the fuel contained within a group of fuelpins within the nuclear reactor core. In this regard, the fuel smeardensity value may be defined by the fuel smear density associated withthe fuel pins contained within one or more fuel assemblies of a nuclearreactor core. For example, the one or more processors 106 of controller102 may generate an initial set of fuel smear density values associatedwith the set of regions located at the initial set of positions in thesimulated BOC core using the one or more design variables of each of theset of regions. Those skilled in the art will recognize that “smeardensity” is the density of nuclear fuel as if it were uniformly“smeared” throughout the inside surface of the fuel cladding. Nuclearfuel smear density is generally described in Alan E. Waltar and AlbertB. Reynolds, Fast Breeder Reactors, 1st ed, Pergamon Press Inc., 1981,p. 121, which has been incorporated above by reference in the entirety.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, the fission gas plenum volumeassociated with one or more pins of one or more fuel assemblies of theBOC core. For example, the one or more processors 106 of controller 102may generate an initial fission gas plenum volume for each fuel pin ofone or more fuel assemblies of the simulated BOC core using the one ormore design variables of each of the set of regions. Those skilled inthe art will recognize that for the purposes of the present disclosure“fission gas plenum” constitutes a reservoir located in a given fuel pinfor collecting fission gas products released from the nuclear fuelcontained within the fuel pin during core operation. A fission gasplenum is generally described in Alan E. Waltar and Albert B. Reynolds,Fast Breeder Reactors, 1st ed, Pergamon Press Inc., 1981, p. 254, whichhas been incorporated above by reference in the entirety.

In another embodiment, the set of nuclear fuel pin dimension values 155may include, but is not limited to, the composition of nuclear fuelcontained within one or more pins of one or more fuel assemblies of thesimulated BOC core 120. For example, the one or more processors 106 ofcontroller 102 may generate an initial set of fuel composition valuesassociated with one or more fuel encompassed by the set of regions 122located at the initial set of positions in the simulated BOC core 120using the one or more design variables of each of the set of regions. Inthis regard, the one or more processors 106 of controller 102 maygenerate an initial fuel composition spatial distribution across thesimulated BOC core 120, as represented by the set of regions 122 locatedat the initial set of positions in the simulated BOC core using the oneor more design variables of each of the set of regions.

The fuel composition values generated by the one or more processors 106may include any fuel composition metric known in the art. It should berecognized by those skilled in the art that “nuclear fuel” in generalmay include both fissionable and non-fissionable material (e.g., fertilematerial or non-fissionable/non-fertile material (e.g., alloying agents,moderating material, and the like)). As such, for the purposes of thepresent disclosure, the term “nuclear fuel” is not limited tofissionable material, but may encompass an entire volume of an object ormaterial used as a fuel source in a nuclear reactor setting. In thisregard, the volume of nuclear fuel may include regions of fissionablematerial, regions of fertile material and/or regions of other material(i.e., non-fertile material), such as, but not limited to, neutronmoderating material and alloying agents.

In one embodiment, the one or more processors 106 of controller 102 maygenerate a initial set of nuclear fuel composition values including therelative amount of fissionable material within each of the set ofregions located at the initial set of positions in the simulated BOCcore using the one or more design variables of each of the set ofregions. For example, the one or more processors 106 of controller 102may generate an initial set of nuclear fuel composition values includingthe relative amount of uranium-235 within each of the set of regions 122located at the initial set of positions in the simulated BOC core 120using the one or more design variables of each of the set of regions. Byway of another example, the one or more processors 106 of controller 102may generate an initial set of nuclear fuel composition values includingthe relative amount of plutonium-239 within each of the set of regions122 located at the initial set of positions in the simulated BOC core120 using the one or more design variables of each of the set ofregions.

In another embodiment, the one or more processors 106 of controller 102may generate a initial set of nuclear fuel composition values includingthe relative amount of fertile material within each of the set ofregions 122 located at the initial set of positions in the simulated BOCcore 120 using the one or more design variables of each of the set ofregions 122. For example, the one or more processors 106 of controller102 may generate an initial set of nuclear fuel composition valuesincluding the relative amount of uranium-238 within each of the set ofregions 122 located at the initial set of positions in the simulated BOCcore 120 using the one or more design variables of each of the set ofregions 122. By way of another example, the one or more processors 106of controller 102 may generate a initial set of nuclear fuel compositionvalues including the relative amount of thorium-232 within each of theset of regions 122 located at the initial set of positions in thesimulated BOC core 120 using the one or more design variables of each ofthe set of regions 122.

In another embodiment, the one or more processors 106 of controller 102may generate an initial set of nuclear fuel composition values includingthe relative amount of constituent elements in a nuclear fuel alloywithin each of the set of regions 122 located at the initial set ofpositions in the simulated BOC core 120 using the one or more designvariables of each of the set of regions 122. Those skilled in the artshould recognize that an alloying agent, such as, but not limited to,zirconium, may be used in metallic nuclear fuels in order to stabilizethe phases (e.g., stabilize the migration of constituent materials) ofthe metallic nuclear fuels. In one embodiment, the one or moreprocessors 106 of controller 102 may generate an initial set of nuclearfuel composition values including the relative amount of uranium andplutonium in a uranium-zirconium alloy contained within each of the setof regions located at the initial set of positions in the simulated BOCcore 120 using the one or more design variables of each of the set ofregions 122. In another embodiment, the one or more processors 106 ofcontroller 102 may generate an initial set of nuclear fuel compositionvalues including the relative amount of uranium, plutonium and zirconiumin a uranium-plutonium-zirconium alloy contained within each of the setof regions located at the initial set of positions in the simulated BOCcore using the one or more design variables of each of the set ofregions 122.

It should be recognized that types of fissile and non-fissile materialsdescribed above should not be interpreted as limitations. Rather, thetypes of fissile and non-fissile material described above are providedmerely for illustrative purposes and it is anticipated that additionalor alternative materials may be suitable for implementation in thepresent invention.

FIG. 1O illustrates a block diagram of reactor core parameterdistributions 159 suitable for calculation by the one or more processors106 of the controller 102, in accordance with one or more embodiments ofthe present invention. In one embodiment, the one or more processors 106of controller 102 are configured to calculate one or more reactor coreparameter distributions of the simulated BOC core 120 based on thegenerated initial set of fuel design parameter values associated withthe set of regions 122 located at the initial set of positions of thesimulated BOC core 120. For example, as shown in FIG. 1B, the programinstructions 105 maintained in memory 108 may include a simulated coreparameter distribution calculator algorithm 136 configured to cause theone or more processors 106 of controller 102 to calculate one or morereactor core parameter distributions of the simulated BOC core 120 basedon the generated initial set of fuel design parameter values 141associated with the set of regions 122 located at the initial set ofpositions of the simulated BOC core 120. In a further embodiment, theone or more processors 106 of the controller 102 may transmit thecalculated one or more reactor core parameter distributions 159 to oneor more databases 107 maintained in memory 108 for storage and lateruse.

The one or more reactor core parameter distributions 159 calculated viathe one or more processors 106 may include any reactor core parameterdistribution known in the art. In one embodiment, the one or moreprocessors 106 may calculate the power density distribution 160 of thesimulated BOC reactor core 120. In another embodiment, the one or moreprocessors 106 may calculate the rate of change of the power densitydistribution 161 of the simulated BOC reactor core 120. The powerdensity and rate of change of power density in a nuclear reactor coreare generally described in Elmer E. Lewis, Fundamentals of NuclearReactor Physics, 1st ed, Elsevier Inc., 2008, pp. 199-213, which isincorporated herein in the entirety.

In one embodiment, the one or more processors 106 may calculate thereactivity distribution 162 of the simulated BOC reactor core 120. Inanother embodiment, the one or more processors 106 may calculate therate of change of the reactivity distribution 163 of the simulated BOCreactor core 120. Reactivity and rate of change of reactivity in anuclear reactor core are generally described in Elmer E. Lewis,Fundamentals of Nuclear Reactor Physics, 1st ed, Elsevier Inc., 2008,pp. 115-234, which has been incorporated above in the entirety.

Referring again to FIGS. 1A-1C, the one or more processors 106 ofcontroller 102 are configured to generate a loading distribution byperforming one or more perturbation processes on the set of regions 122of the simulated BOC core 120, in accordance with an embodiment of thepresent invention. In this regard, the implemented perturbation processallows the system 100 to determine a subsequent set of positions for theset of regions 122 within the simulated BOC core.

In one embodiment, as shown in FIG. 1B, the program instructions 105maintained in memory 108 may include a simulated loading distributiongenerator algorithm 138 configured to cause the one or more processors106 of controller 102 to generate a loading distribution by performingone or more perturbation processes on the set of regions 122 of thesimulated BOC core 120. In another embodiment, as shown in FIG. 1C, theone or more processors 106 of the controller 102 may transmit thegenerated loading distribution 143 (e.g., distribution of nuclear fuelcomposition throughout the simulated nuclear reactor core 120) to one ormore databases 107 of memory 108 for storage and later use.

In one embodiment, the subsequent set of positions serve to reduce thedeviation metric (e.g., difference, spatially averaged difference,maximum difference, minimum difference, aggregated global deviationmetric and the like) between the one or more calculated reactor coredistributions of the simulated BOC core and the received one or morereactor core parameter distributions associated with a state of a coreof a nuclear reactor (i.e., reference nuclear reactor) below a selectedtolerance level.

In another embodiment, the subsequent set of positions may define asuitable loading distribution for the simulated BOC core 120. Forexample, the subsequent set of region positions may define a suitablecore loading distribution in situations where the subsequent set ofpositions (i.e., positions of regions after one or more perturbationcycles) of the set of regions within the simulated core produce one ormore calculated loading distributions 143 that sufficiently converge(e.g., sufficiently converge below a selected tolerance level) towardthe one or more reference reactor core parameter distributions 103 fromthe core parameter distribution source 104. In this setting, thesubsequent set of positions may be utilized as the “final” set ofpositions of the one or more regions 122 in an associated nuclearreactor core (see core 202 described further herein).

FIG. 1P illustrates a flow diagram depicting steps of a perturbationprocess 170 suitable for determining a subsequent set of positions ofthe regions 122 of the simulated reactor core 120, in accordance with anembodiment of the present invention. In a first step 171, the one ormore processors 106 of controller 102 may receive one or more referencereactor core parameter distributions. For example, as describedthroughout the present disclosure, the one or more processors 106 ofcontroller 102 may receive one or more reference reactor core parameterdistributions 103 from the core parameter distribution source 104. Forinstance, the one or more reference reactor core parameter distributionsmay include an equilibrium distribution of a reference nuclear reactorcore (e.g., operated reactor core).

In a second step 172, the one or more processors 106 of controller 102may calculate a first reactor core parameter distribution (or a firstset of reactor core parameter distributions). For example, utilizing thevarious methods and embodiments as described throughout the presentdisclosure, the one or more processors 106 of controller 102 maycalculate a first reactor core parameter distribution based on adistribution of regions 122 (e.g., regions containing one or more fuelassemblies 124) containing “fresh” nuclear fuel (e.g., unburned nuclearfuel or enriched nuclear fuel) or recycled nuclear fuel throughout thesimulated nuclear core 120.

In a third step 173, the one or more processors 106 of the controller102 may compare the first calculated reactor core parameter distributioncalculated in step 172 to the received reference reactor core parameterdistribution of step 171. For example, the one or more processors 106 ofthe controller 102 may compare a first calculated reactor core powerdensity distribution (calculated in step 172) to a received referencereactor core power density distribution (received in step 171).

Further, the one or more processors 106 may calculate at least onedeviation metric between at least a portion of the first calculatedreactor core parameter distribution and a portion of the receivedreference reactor core parameter distribution. It is noted herein thatthe deviation metric calculated by the one or more processors 106 mayinclude any metric known in the art suitable for quantifying adifference or deviation between all or a portion of the first calculatedreactor core parameter distribution and the received reference reactorcore parameter distribution. For example, the deviation metric mayinclude, but is not limited to, a difference (e.g., difference at acommon position), a relative difference, a ratio, an averaged difference(e.g., spatially averaged difference), maximum difference (e.g., maximumdifference between any two or more common positions), minimum difference(e.g., minimum difference between two or more common positions),aggregated deviation (e.g., global deviation metric) or any otherdeviation metric known in the art.

It is recognized herein that both the first calculated reactor coreparameter distribution and the received reference reactor core parameterdistribution may each consist of a three-dimensional distribution of agiven reactor core parameter throughout a nuclear reactor core. As such,a comparison 173 between the first calculated reactor core parameterdistribution and the received reference reactor core parameterdistribution may include any comparison technique known in the artsuitable for comparing two or more three-dimensional varyingdistributions.

In one embodiment, the comparison may include comparing the reactor coreparameter distributions along a selected direction in the simulated coreand the reference core. For example, the comparison may includecomparing the reactor core parameter distributions along at leastsimilar radial lines running through the simulated and reference cores.It is noted herein that this approach effectively reduces the threedimensional comparison to a one-dimensional comparison. It is furthernoted that a number of comparisons, each along a different direction,may be made between the simulated and reference cores. Then, themultiple one-dimensional comparisons may be aggregated in order toprovide a global deviation metric representative of the overalldeviation between the first calculated reactor core parameterdistribution and the reference reactor core parameter distribution.

In another embodiment, the comparison may include comparing the reactorcore parameter distributions across a selected plane, or cross-section,in the simulated core and the reference core. For example, thecomparison may include comparing the reactor core parameterdistributions across at least similar cross-sections running through thesimulated and reference cores. It is noted herein that this approacheffectively reduces the three-dimensional comparison to atwo-dimensional comparison. It is further noted that a number ofcomparisons, each at a different cross-section, may be made between thesimulated and reference cores. Then, the multiple two-dimensionalcomparisons may be aggregated in order to provide a global deviationmetric representative of the overall deviation between the firstcalculated reactor core parameter distribution and the reference reactorcore parameter distribution.

In another embodiment, the comparison may include comparingdistributions at each of the set of regions 122 (e.g., regions 122 inFIG. 1I-1K) in the simulated core and the reference core. For example,the comparison may include generating an aggregated deviation metricbetween the first calculated reactor core parameter distribution and thereceived reference reactor core parameter distribution by calculating adeviation metric between the two distributions at each of the sets ofregions 122. Then, deviation metrics collected in the multiplecomparisons from each region may be statistically aggregated to providea global deviation metric representative of the overall deviationbetween the first calculated reactor core parameter distribution and thereference reactor core parameter distribution. In another embodiment,the comparison may include comparing averaged deviation values (e.g.,averaged difference values) for one or more reactor core parameterdistributions extracted from selected volumes (e.g., regions 122 orgroups of regions 122) of the reference and simulated cores.

Upon comparing the first calculated reactor core parameter distributionand the reference reactor core parameter distribution, the one or moreprocessors 106 of controller 102 may determine whether the deviationmetric calculated between the first calculated reactor core parameterdistribution and the reference reactor core parameter distribution isabove, at or below a selected tolerance level. In the event that thedeviation metric is at or below the selected tolerance level, theperturbation procedure ends 174. In the event that the deviation metricis above the selected tolerance level, the perturbation procedure movesto step 175.

In a fourth step 175, the one or more processors 106 of the controller102 may vary the spatial position of one or more of the set of regions122 (e.g., regions containing one or more simulated fuel assemblies 124)of the simulated BOC core 120. In this regard, the one or moreprocessors 106 of the controller 102 may “perturb” the regions 122. Itis recognized herein that the position of the regions 122 may beperturbed along one or more directions in any manner known in the art.

In a fifth step 176, the one or more processors 106 of the controller102 may calculate an additional reactor core parameter distribution (oran additional set of reactor core parameter distributions) based on theperturbed positions of regions 122 achieved in step 175. For example,utilizing the various methods and embodiments as described throughoutthe present disclosure, the one or more processors 106 of controller 102may calculate an additional reactor core parameter distribution based ona distribution of regions 122, containing fresh or recycled nuclearfuel, at their new positions (“new” relative to positions of step 172)achieved in step 175.

In a sixth step 177, the one or more processors 106 of the controller102 may compare the additional calculated reactor core parameterdistribution found in step 176 to the received reference reactor coreparameter distribution of step 171. For example, the one or moreprocessors 106 of the controller 102 may compare an additionalcalculated reactor core power density distribution (calculated in step176) to a received reference reactor core power density distribution(received in step 171) in a manner similar to that described in step 173above.

Upon comparing the additional calculated reactor core parameterdistribution to the reference reactor core parameter distribution, theone or more processors 106 of controller 102 may determine whether thedeviation metric between the additional calculated reactor coreparameter distribution and the reference reactor core parameterdistribution is above, at or below the selected tolerance level, asdescribed above. In the event that the deviation metric is at or belowthe selected tolerance level, the perturbation procedure may end 178. Inthe event that the deviation metric is above the selected tolerancelevel, the perturbation procedure may repeat, starting again with step175, until the Nth calculated reactor core parameter distributionconverges toward the reference core parameter distribution to a level ator below the selected threshold value. In this regard, the positions ofthe regions 122 define the distribution of fresh or recycled nuclearfuel that produces a reactor core parameter distribution that deviatesfrom the reference reactor core parameter distribution (e.g.,equilibrium distribution) by a magnitude equal to or less than theselected tolerance value (e.g., a selected level of accuracy).

In another embodiment, the perturbation process 170 may implement linearrates of change analysis on a iteration steps after the first iterationstep. For example, the perturbation process 170 may implement linearrates of change analysis on a iteration steps on the second iterationstep. For instance, on a second iteration step, the perturbed resultsmay be compared to the results of the first iteration. Based on thedifference observed between the first and second steps, a linear rate ofchange for the regions 122 may be calculated. In turn, the linear rateof change is utilized in the next perturbation step. Further, thisprocess may be repeated until the reactor core parameter distributiondeviates from the reference reactor core parameter distribution (e.g.,equilibrium distribution) by a magnitude equal to or less than theselected tolerance value (e.g., a selected level of accuracy).

It is further recognized herein that reactor core parameterdistributions, such as reactivity and power density distributions, arenot generally unique. As such, multiple reactor states may providesimilar results. In one embodiment, the present invention may act topreferentially select solutions sufficiently near critical, wherebyk_(eff)=1. In this regard, a second level of iteration may activatefollowing the convergence of the first iteration (described above) inorder to adjust the enrichment distribution within the simulated core120 such that simulated core is critical or at least near-critical.Further, the present invention may execute these steps multiple times inorder to properly converge on a critical distribution that mirrors thedistribution of the reference nuclear reactor in the selected state(e.g., equilibrium).

Referring again to FIG. 1A, the one or more processors 106 may reportthe generated loading distribution including the subsequent set ofpositions of the set of regions of the simulated BOC core 120 found inthe perturbation process to one or more associated devices or systems.

In one embodiment, the one or more processors 106 of controller 102 mayreport the subsequent set of positions of the set of regions 122 of thesimulated BOC core to a display device 116. In another embodiment, theone or more processors 106 of controller 102 may report the set ofpositions of the set of regions 122 at each iterative step of theperturbation process of the simulated BOC core to a display device 116.

The display device may include any visual display device known in theart. For example, the display device 116 may include, but is not limitedto, a display device 116 of a user interface device 114 communicativelycoupled to the controller 102. The display device 116 may include anyvisual or audio display device known in the art. For example, in thecase of visual display, the display device may include, but is notlimited to a liquid crystal display (LCD), one or more light emittingdiodes (LEDs), one or more organic LEDs (OLEDs), a cathode rate tube(CRT) or the like. Further, the interface device 114 may include anyuser input device 118 known in the art. For example, the one or moreuser input device 118 may include a keyboard, a touchpad, a touchscreenintegrated with a display device, a mouse, and the like.

In another embodiment, the one or more processors 106 of controller 102may report the loading distribution results including the subsequent setof positions of the set of regions 122 of the simulated BOC core to oneor more memory devices. For example, the one or more processors 106 maytransmit the loading distribution results 143 of the perturbationprocess to a database 107 maintained in memory 108 of controller 102. Byway of another example, the one or more processors 106 may transmit theloading distribution results 143 of the perturbation process to adatabase maintained in memory of a remote system (e.g., remote server)communicatively coupled to controller 102.

In another embodiment, the one or more processors 106 of controller 102may report the set of positions of the set of regions 122 at eachiterative step of the perturbation process of the simulated BOC core toone or more memory devices. For example, the one or more processors 106may transmit the set of positions of the set of regions 122 at eachiterative step of the perturbation process of the simulated BOC core toa database 107 maintained in memory 108 of controller 102. By way ofanother example, the one or more processors 106 may transmit the set ofpositions of the set of regions 122 at each iterative step of theperturbation process of the simulated BOC core to a database maintainedin memory of a remote system (e.g., remote server) communicativelycoupled to controller 102.

In another embodiment, the one or more processors 106 of controller 102may report the loading distribution results including the subsequent setof positions of the set of regions 122 of the simulated BOC core to anoperation system of an associated nuclear reactor 101. For example, theone or more processors 106 may transmit the loading distribution results143 of the perturbation process to control system 180 of nuclear reactor101.

In another embodiment, the one or more processors 106 of controller 102may report the set of positions of the set of regions 122 at eachiterative step of the perturbation process of the simulated BOC core toa control system 180 of an associated nuclear reactor 101. For example,the one or more processors 106 may transmit the set of positions of theset of regions 122 at each iterative step of the perturbation process ofthe simulated BOC core to control system 180 of nuclear reactor 101.

Referring generally to FIGS. 2A-2D, a nuclear reactor system 200equipped with loading distribution generation capabilities is described,in accordance with one embodiment of the present invention. In oneaspect, the system 200 is suitable for generating a loading distribution(as described previously herein). In turn, the loading distributiongenerated by the system 200 may then be utilized to configure a nuclearreactor core 202 (e.g., arrange one or more fuel assemblies 208 of core202 or initially load one or more fuel assemblies 208 of core 202)associated with the controller 102 of system 200. In this regard, theconfiguration of nuclear reactor core 202 is executed such that the core202 of the reactor begins cycle operation (e.g., beginning of lifeoperation) in a state consistent with (i.e., within a selected tolerancelevel) the received reactor core parameter distribution associated witha selected state (e.g., equilibrium state) of a core of a referencenuclear reactor.

Applicant notes herein that the various embodiments and examplesprovided throughout the present disclosure should be interpreted toextend to system 200. As previously described herein, the system 200 mayinclude controller 102 communicatively coupled to a core parameterdistribution source 104 (e.g., core parameter distribution databasemaintained in memory). Further, the controller 102 is configured toreceive one or more reactor core parameter distributions 103 (e.g.,power density distribution or reactivity distribution) associated with astate, such as an equilibrium state, of a core of a reference nuclearreactor (e.g., reference breed-and-burn nuclear reactor) from the coreparameter distribution source 104. In addition, the controller 102 isconfigured to generate an initial fuel loading distribution for asimulated BOC core of a nuclear reactor. The controller 102 is furtherconfigured to select an initial set of positions associated with a setof regions 122 within the simulated BOC core 120 of the nuclear reactor.Further, the controller 102 is configured to generate an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions 122. In addition, the controller 102 isconfigured to calculate a reactor core parameter distribution of thesimulated BOC 120 core based on the generated initial set of fuel designparameter values associated with the set of regions 122 located at theinitial set of positions of the simulated BOC core 120. Further, thecontroller 102 is configured to generate a loading distribution byperforming one or more perturbation processes (e.g., perturbationprocess illustrated in FIG. 1P) on the set of regions 122 of thesimulated BOC core 120 in order to determine a subsequent set ofpositions for the set of regions 122 within the simulated BOC core 120.

In a further aspect of the present invention, the system 200 may includea nuclear reactor 101 associated with controller 102. In one embodiment,the nuclear reactor 101 includes a nuclear reactor core 202. In afurther embodiment, the nuclear reactor core 202 includes a set of fuelassemblies 208. In a further embodiment, the fuel assemblies 208 ofreactor core 202 are arrangeable according to the nuclear fuel loadingdistribution generated by the one or more processors 106 of thecontroller 102, as described previously herein. Further, as describedpreviously herein, the nuclear fuel loading distribution may include asubsequent set of positions of regions 122 with the simulated BOC core120. As described previously herein, the subsequent set of positions ofregions 122 may act to cause the reactor core parameter distribution ofthe simulated BOC core 120 to converge toward the reactor core parameterdistribution received from the core of the reference reactor within apreselected tolerance level. In this regard, the subsequent set ofpositions of regions 122 serve to form a reactor core parameterdistribution that “matches” the reactor core parameter distribution froma given reference nuclear reactor in a selected state, such as anequilibrium state.

In one embodiment, as shown in FIGS. 2A-2B, the system 200 includes afuel handler 204 communicatively coupled (e.g., coupled directly orindirectly) to one or more processors 106 of controller 102. In afurther embodiment, the fuel handler 204 is configured to arrange atleast one fuel assembly 208 of the nuclear reactor core 202 of reactor101 according to the subsequent set of positions of the set of regionsof the simulated BOC core generated by controller 102. It is notedherein that the fuel handler 204 may include any nuclear fuel assemblyhandler, or nuclear fuel assembly handling system, known in the art. Forexample, the nuclear fuel handler 204 may include any nuclear fuelassembly handler/handling system capable of “gripping” a fuel assemblyand moving the fuel assembly from an initial location to a new location.In this regard, the fuel handler 204 is capable of re-arranging fuelassemblies already present in the reactor core 202 or removing fuelassemblies from the reactor core 202 and inserting fuel assemblies intothe reactor core 202.

FIG. 2C illustrates a block diagram of one or more sets of programinstructions 210 maintained in memory 108 and configured to carry outone or more steps described throughout the present disclosure. Asdescribed previously herein, the program instructions 210 maintained inmemory 108 may include an initial loading distribution generatoralgorithm 130, an initial region position selector algorithm 132, aninitial fuel design parameter generator algorithm 134, a simulated coreparameter distribution calculator algorithm 136 and a simulated loadingdistribution generator algorithm 138. In a further embodiment, theprogram instructions 210 of system 200 may include, but are not limitedto, a fuel assembly arranger algorithm 211 configured to direct the fuelassembly handler 204 to arrange one or more fuel assemblies 208 of thecore 202 of reactor 101 in response to the output of the simulatedloading distribution generator algorithm 138.

Referring again to FIGS. 2A-2B, the system 200 may include, but is notlimited to, a fuel handler controller 206. In one embodiment, the one ormore processors 106 of controller 102 are placed in indirectcommunication with fuel handler 204 via fuel handler controller 206. Inthis regard, as shown in FIGS. 2A and 2B, the one or more processors 106of controller 102 are configured to transmit one or more signals 207indicative of the subsequent set of positions of the set of regions ofthe simulated BOC core 120 generated by controller 102 to the fuelhandler controller 206. In turn, the fuel handler controller 206 mayreceive the one or more signals 207 from controller 102 and direct thefuel handler 204 (e.g., via signal 209) to arrange the one or more fuelassemblies 208 of the reactor core 202 in accordance with the subsequentset of positions of the set of regions 122 of the simulated BOC core 120encoded in the transmitted signal. In this regard, upon generating asuitable loading distribution, the controller 102 may direct the fuelhandler 204 to arrange the constituents of the core 202 such that theymatch the loading distribution generated by controller 102.

In an alternative embodiment, although not shown, the one or moreprocessors 106 of controller 102 are placed in indirect communicationwith fuel handler 204 via control system 180 of the nuclear reactor 101.In one embodiment, the controller 102 may indirectly transmitinstructions to fuel handler 204 via the reactor control system 180. Inthis regard, the one or more processors 106 of controller 102 areconfigured to transmit one or more signals (not shown) indicative of thesubsequent set of positions of the set of regions of the simulated BOCcore generated by controller 102 to the control system 180 of thenuclear reactor 101. In turn, the control system 180 of the nuclearreactor 101 may receive the one or more signals from controller 102 anddirect the fuel handler 204 to arrange the one or more fuel assemblies208 of the reactor core 202 in accordance with the subsequent set ofpositions of the set of regions of the simulated BOC core encoded in thetransmitted signal.

In another embodiment, although not shown, the one or more processors106 of controller 102 are placed in direct communication with fuelhandler 204. In one embodiment, the controller 102 may directly transmitinstructions to fuel handler 204. In this regard, the one or moreprocessors 106 of controller 102 are configured to transmit one or moresignals (not shown) indicative of the subsequent set of positions of theset of regions of the simulated BOC core generated by controller 102directly to the fuel handler 204. In this manner, the one or moreprocessors 106 of controller 102 may direct the fuel handler 204 toarrange the one or more fuel assemblies 208 of the reactor core 202 inaccordance with the subsequent set of positions of the set of regions ofthe simulated BOC core encoded in the transmitted signal. It isrecognized herein that the functions of the fuel handler controller 206(e.g., software/firmware necessary to control fuel handler 204) asdescribed throughout the present disclosure may be integrated within thecontroller 102. In this regard, the fuel handler controller 206 may beconfigured as a module of the controller 102.

In another embodiment, the controller 102 may be integrated within oneor more operating systems of the nuclear reactor 101. For example, thevarious functions of controller 102 may be integrated within the controlsystem 180 of the nuclear reactor 101. In this regard, the controller102 may be configured as a module of the control system 180.

Referring again to FIGS. 2A-2B, the one or more processors 106 ofcontroller 102 may direct the fuel handler 204 to arrange one or morefuel assemblies 208 by translation of one or more fuel assemblies 208.In one embodiment, the one or more processors 106 of controller 102 areconfigured to direct the fuel handler 204 to translate one or more fuelassemblies 208 of the core 202 of the nuclear reactor 101 from aninitial location to a subsequent location according to the subsequentset of positions of the set of regions of the simulated BOC core. Forexample, as shown in FIG. 2B, the one or more processors 106 ofcontroller 102 may direct the fuel handler 204 to mechanically couple tofuel assembly 212 via gripper unit 214. In turn, the fuel handler 204may withdraw the fuel assembly 212 from the core 202 and translate thefuel assembly 212 to a different location. Upon reaching the newlocation, the fuel handler 204 may then re-insert the fuel assembly 212into to new location. It is recognized herein that in order for the newlocation to be available for re-insertion of assembly 212 the assembly(not shown) previously occupying the location must first be removed(e.g., removed by a second gripper of fuel handler 204 or an additionalfuel handler (not shown)). In this regard, the fuel handler 204 (ormultiple fuel handlers) may arrange (or re-arrange) all or a portion ofthe fuel assemblies 208 of the of the core 202 of the nuclear reactor101 according to the subsequent set of positions of the set of regionsof the simulated BOC core 120 generated by the controller 102.

In another embodiment, the one or more processors 106 of controller 102may direct the fuel handler 204 to arrange one or more fuel assemblies208 by replacing one or more fuel assemblies 208. In one embodiment, theone or more processors 106 of controller 102 are configured to directthe fuel handler 204 to replace one or more fuel assemblies 208 of thecore 202 of the nuclear reactor 101 according to the subsequent set ofpositions of the set of regions of the simulated BOC core 120. Forexample, as shown in FIG. 2B, the one or more processors 106 ofcontroller 102 may direct the gripper unit 214 of the fuel handler 204to mechanically couple to fuel assembly 212. In turn, the fuel handler204 may withdraw the fuel assembly 212 from the core 202 and move thefuel assembly 212 to a fuel assembly storage unit (not shown). Then, thegripper unit 214 of fuel handler 204 (or an additional fuel handler) maymechanically couple to a “new” fuel assembly (not shown) and move thenew fuel assembly into the location of the removed fuel assembly 212 oranother location. In this regard, the fuel handler 204 (or multiple fuelhandlers) may replace all or a portion of the fuel assemblies 208 of theof the core 202 of the nuclear reactor 101 according to the subsequentset of positions of the set of regions of the simulated BOC core 120generated by the controller 102.

In another embodiment, the one or more processors 106 of controller 102may direct the fuel handler 204 to arrange one or more fuel assemblies208 by loading one or more fuel assemblies 208 into the core 202. In oneembodiment, the one or more processors 106 of controller 102 areconfigured to direct the fuel handler 204 to freshly load (i.e., loadfor the first time) one or more fuel assemblies 208 of the core 202 ofthe nuclear reactor 101 according to the subsequent set of positions ofthe set of regions of the simulated BOC core 120. For example, the oneor more processors 106 of controller 102 may direct the gripper unit 214of the fuel handler 204 to mechanically couple to a fuel assembly (notshown) stored outside of the reactor core 202. In turn, the fuel handler204 may move the fuel assembly to a location consistent with thesubsequent set of positions of the set of regions of the simulated BOCcore 120 generated by the controller 102. In this regard, the fuelhandler 204 (or multiple fuel handlers) may load all or a portion of thefuel assemblies 208 of the of the core 202 of the nuclear reactor 101according to the subsequent set of positions of the set of regions ofthe simulated BOC core 120 generated by the controller 102.

In another embodiment, the fuel handler 204 may be controlled via userinput. For example, a user may review a nuclear fuel loadingdistribution generated by controller 102 on a display 116. In responseto the nuclear fuel loading distribution, the user may choose to accept,reject or modify the displayed nuclear fuel loading distribution. Forinstance, upon being presented with a suitable nuclear fuel loadingdistribution, the user may approve the suitable nuclear fuel loadingdistribution via the user input device 118. In turn, the one or moreprocessors 106 of controller 102 may direct the fuel handler 204 toimplement the approved nuclear fuel loading distribution, as describedthroughout the present disclosure. In another instance, upon beingpresented with an undesired nuclear fuel loading distribution, the usermay reject the undesired nuclear fuel loading distribution via the userinput device 118. In turn, the one or more processors 106 of controller102 may terminate or repeat the core simulation/handling procedure ofthe present invention. In another instance, upon being presented with anundesired nuclear fuel loading distribution, the user may modify theundesired nuclear fuel loading distribution via the user input device118. For example, the user may accept a portion of the provided loadingdistribution, while altering one or more other portions of the loadingdistribution. For instance, the user may alter, or re-arrange (e.g., viauser input device 118 and/or display 116), the arrangement of the fuelassemblies or fuel assembly ensembles of the nuclear fuel loadingdistribution provided by controller 102. In turn, the one or moreprocessors 106 of controller 102 may direct the fuel handler 204 toimplement the user-altered nuclear fuel loading distribution.

FIG. 2D illustrates the types of nuclear reactors suitable for corearrangement of the present invention, in accordance with one or moreembodiments of the present invention. The nuclear reactor 101 of system200 may include any nuclear reactor known in the art. In one embodiment,the nuclear reactor 101 may include, but is not limited to, a thermalnuclear reactor 214. In another embodiment, the nuclear reactor 101 mayinclude, but is not limited to, a fast nuclear reactor 216. In anotherembodiment, the nuclear reactor 101 may include, but is not limited to,a breed-and-burn nuclear reactor 218. In another embodiment, the nuclearreactor 101 may include, but is not limited to, a traveling wave nuclearreactor 220.

It is recognized herein that the fuel assembly configuration of thereactor core 202 of the nuclear reactor 101 of system 200 may take onany configuration known in the art. As such, the number, shape, size andarrangement of the fuel assemblies 208 within the reactor core 202 ofreactor 101 may take on any configuration known in the art. For example,the fuel assemblies 208 may include hexagonoid-shaped fuel assembliesarranged in a hexagonal array configuration, as depicted in FIGS. 2A-2B.In another embodiment, each fuel assembly 208 of the reactor core 202 ofthe nuclear reactor 101 of system 200 may include one or more fuel pins(not shown). It is recognized that the number, shape, size andarrangement of the fuel pins within each fuel assembly 208 may take onany configuration known in the art. For example, the fuel pins of eachfuel assembly 208 may include cylindrically shaped fuel pins arranged ina close-packed configuration within each fuel assembly, similar to thesimulated arrangement depicted in FIG. 1G.

In another embodiment, the one or more processors 106 of controller 102are configured to generate a core 120 simulating environment having atleast some simulated physical characteristics substantially similar tosome of the physical characteristics of reactor core 202 of reactor 101.For example, in settings where the reactor core 202 consists ofhexagonoid-shaped fuel assemblies arranged in a hexagonal arraystructure, the program instructions 210 may be suitable for causing theone or more one or more processors 106 of controller 102 to generate areactor core 120 simulating environment having hexagonoid-shaped fuelassemblies arranged in a hexagonal array structure. In a general sense,the program instructions 210 are configured to cause the one or moreprocessors 106 of controller 102 to pattern the simulated reactor core120 after the associated reactor core 202 within a selected accuracylevel for various selected characteristics (e.g., type of fuelassemblies (e.g., size, shape, and etc.), number of fuel assemblies,arrangement of fuel assemblies and the like). Then, once the one or moreprocessors 106 of controller 102 have established a reactor coresimulating environment at least similar to the reactor core 202, the oneor more processors 106 may proceed to execute the core simulationprocess steps as described throughout the present invention.

Referring generally to FIGS. 3A-3D, a nuclear reactor system 300equipped with operational compliance feedback capabilities is described,in accordance with one embodiment of the present invention. In oneembodiment, the system 300 of the present invention is directed, atleast in part, to measuring the operation compliance of a reactor coreof the nuclear reactor of system 300. Further, the system 300 may act toprovide an additional, or “new,” nuclear fuel loading distributionsuitable for adjusting the nuclear fuel loading distribution of thereactor core 202 in order to bring the reactor core 202 into a state ofcompliance.

In one aspect, system 300 may include controller 102 communicativelycoupled to a core parameter distribution source 104 and configured todetermine an initial nuclear fuel loading distribution of the nuclearreactor core 202 utilizing a BOC simulation process to generate asimulated BOC nuclear reactor core 120. Applicant notes that system 300may determine an initial loading distribution utilizing the varioussystems and methods described throughout the present disclosure. Assuch, the various embodiments and examples provided throughout thepresent disclosure should be interpreted to extend to system 300.

In another aspect, the system 300 may include a reactor core measurementsystem 300 (e.g., thermal measurement system, pressure measurementsystem and the like) communicatively coupled to controller 102 andsuitable for measuring one or more state variables of one or moreportions of reactor core 202. In another aspect, the controller 102 isfurther configured to compare (e.g., calculate a deviation metric) agenerated measured reactor core parameter distribution acquired from thereactor core 202 to one or more reactor core parameter distributions ofa simulated operated nuclear reactor core. In another aspect, thecontroller 102 is further configured to determine an operationalcompliance state (e.g., in-compliance or out-of-compliance) of the core202 of the nuclear reactor 101 using the comparison between thegenerated measured reactor core parameter distribution acquired fromreactor core 202 and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core 120. In afurther aspect, the nuclear reactor core 202 of nuclear reactor 101 mayinclude a set of fuel assemblies 208 arrangeable according to a set ofsimulated positions of a set of regions of at least one of the simulatedBOC nuclear reactor core and an additional simulated nuclear reactorcore. In one embodiment, prior to operation, the fuel assemblies 208 ofreactor core 202 are arrangeable according to an initial fuel loadingdistribution of the simulated BOC nuclear reactor core 120 generated bythe one or more processors 106 of the controller 102. In anotherembodiment, follow a period of operation, the fuel assemblies 208 ofreactor core 202 are arrangeable according to an additional fuel loadingdistribution (e.g., additional fuel loading distribution generated inresponse to an out-of-compliance reactor operation state) of anadditional simulated nuclear reactor core generated by the one or moreprocessors 106 of controller 102. In one embodiment, the fuel handler204 of system 300 is further configured to arrange one or more fuelassemblies of the reactor core 202 according to an initial fuel loadingdistribution of the simulated BOC nuclear reactor core 120 or anadditional loading distribution of an additional simulated core.

FIG. 3B illustrates a block diagram of one or more sets of programinstructions 304 maintained in memory 108 and configured to carry outone or more steps described throughout the present disclosure. In oneembodiment, the program instructions 304 maintained in memory 108 mayinclude a core loading distribution generator algorithm 306 configuredto generate an initial loading distribution for the nuclear reactor core202 of reactor 101 using a BOC simulation process to generate asimulated BOC nuclear reactor core (as discussed previously herein). Inanother embodiment, the program instructions 304 may include a measuredreactor core distribution generator algorithm 308 configured to generatea measured reactor core parameter distribution based on one or moremeasurements of one or more reactor core parameters at one or morelocations within the core 202 of the nuclear reactor 101 after thenuclear reactor core 202 is operated for a given time interval. Inanother embodiment, the program instructions 304 may include a reactorcore parameter distribution comparator algorithm 310 configured tocompare the generated measured reactor core parameter distributionoutputted from generator 308 to one or more reactor core parameterdistributions of the simulated operated nuclear reactor core. In anotherembodiment, the program instructions 304 may include an operationcompliance determiner algorithm 312 configured to determine anoperational compliance state of the core 202 of the nuclear reactor 101based on the comparison between the generated measured reactor coreparameter distribution and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core. In afurther embodiment, the program instructions 304 may include a fuelassembly handler algorithm 313 configured to arrange one or more fuelassemblies 208 of the reactor core 202 of reactor 101 in accordance withthe simulated BOC core 120 and/or an additional simulated core,described in greater detail further herein

Referring again to FIG. 3A, in one embodiment, the reactor coremeasurement system 302 is configured to measure one or more statevariable values of the reactor core 202 at one or more locations withinthe reactor core 202. The reactor core measurement system 302 mayinclude any measurement system known in the art capable of measuring oneor more state variables of one or more portions of the reactor core 202.In one embodiment, as shown in FIG. 3C, the reactor core measurementsystem 302 may include a thermal measurement system 314 configured tomeasure one or more thermal characteristics (e.g., temperature,rate-of-change of temperature) of a portion of nuclear fuel materialwithin the reactor core 202 at one or more locations within the reactorcore 202. For example, the thermal measurement system 314 may includeone or more thermal measurement devices configured to measure thetemperature or rate-of-change of temperature at one or more selectedlocations within the reactor core 202. For instance, the thermalmeasurement system 314 may include, but is not limited to, one or morethermocouple devices or one or more resistance based thermal detectiondevices (i.e., RTDs) configured to measure the temperature orrate-of-change of temperature at one or more selected locations withinthe reactor core 202.

In another embodiment, as shown in FIG. 3C, the reactor core measurementsystem 302 may include a pressure measurement system 316 configured tomeasure one or more pressure characteristics (e.g., pressure orrate-of-change of pressure) of a portion of nuclear fuel material withinreactor core 202 at one or more locations within the reactor core 202.For example, the pressure measurement system 316 may include one or morepressure measurement devices configured to measure the pressure orrate-of-change of pressure at one or more selected locations within thereactor core 202. For example, the pressure measurement system 316 mayinclude, but is not limited to, one or more transducer pressure sensorsconfigured to measure the pressure or rate-of-change of pressure at oneor more selected locations within the reactor core 202.

In another embodiment, as shown in FIG. 3C, the reactor core measurementsystem 302 may include a neutron flux measurement system 318 configuredto measure one or more neutron characteristics (e.g., neutron flux orrate-of-change of neutron flux) of a portion of nuclear fuel materialwithin reactor core 202 at one or more locations within the reactor core202. For example, the neutron flux measurement system 318 may includeone or more neutron flux measurement devices configured to measure theneutron flux or rate-of-change of neutron flux at one or more selectedlocations within the reactor core 202. For example, the neutron fluxmeasurement system 316 may include, but is not limited to, one orfission detectors (e.g., in-core micropocket fission detectors)configured to measure the neutron flux or rate-of-change of neutron fluxat one or more selected locations within the reactor core 202.

In another embodiment, the reactor core measurement system 302 mayinclude a set of measurement devices (e.g., thermal measurement devices,pressure measurement devices, neutron flux measurement devices and thelike) each positioned at different locations within the reactor core202. In this regard, the set of measurement devices of the measurementsystem 302 may form an array within the nuclear reactor core 202suitable for measuring one or more values of one or more selected statevariables of the reactor core 202 across the spatial extent (e.g., alongx-direction, y-direction, and/or z-direction) of the nuclear reactorcore 202. Utilizing the spatially resolved measurements of the one ormore state variables, the measurement system 302 (or the one or moreprocessors 106 of controller 102) may build up the spatial dependence ofone or more state variables of the reactor core 202.

For example, the reactor core measurement system 302 may include a setof thermal measurement devices of a thermal measurement system 314 eachpositioned at different locations within the reactor core 202. In thisregard, the set of thermal measurement devices may form an array withinthe nuclear reactor core 202 suitable for measuring one or more thermalcharacteristics across the spatial extent of the nuclear reactor core202. Utilizing the spatially resolved measurements of the one or morethermal characteristics, the thermal measurement system 314 (or the oneor more processors 106 of controller 102) may build up the spatialdependence of one or more thermal characteristics of the reactor core202.

By way of another example, the reactor core measurement system 302 mayinclude a set of pressure measurement devices of a pressure measurementsystem 316 each positioned at different locations within the reactorcore 202. In this regard, the set of pressure sensors may form an arraywithin the nuclear reactor core 202 suitable for measuring one or morepressure characteristics across the spatial extent of the nuclearreactor core 202. Utilizing the spatially resolved measurements of theone or more pressure characteristics, the pressure measurement system316 (or the one or more processors 106 of controller 102) may build upthe spatial dependence of one or more pressure characteristics of thereactor core 202.

By way of another example, the reactor core measurement system 302 mayinclude a set of neutron flux measurement devices of a neutron fluxmeasurement system 318 each positioned at different locations within thereactor core 202. In this regard, the set of neutron flux detectors(e.g., multiple in-core micropocket fission detectors (MPFD)) may forman array within the nuclear reactor core 202 suitable for measuring oneor more neutron flux characteristics across the spatial extent of thenuclear reactor core 202. Utilizing the spatially resolved measurementsof the one or more neutron flux characteristics, the neutron fluxmeasurement system 318 (or the one or more processors 106 of controller102) may build up the spatial dependence of one or more neutron fluxcharacteristics of the reactor core 202.

In one embodiment, one or more the measurement devices 303 of thereactor core measurement system 302 may be positioned in a region of thereactor core 202 between two or more fuel assemblies 208. In anotherembodiment, each of the measurement devices 303 of the reactor coremeasurement system 302 may be affixed to the outside portion of a fuelassembly 208 of the reactor core 202. In another embodiment, each of themeasurement devices 303 of the reactor core measurement system 302 maybe positioned within a fuel assembly 208 of the reactor core 202. Forinstance, each measurement devices 303 may be affixed to an internalsurface of a fuel assembly 208 or between two or more fuel pins of agiven fuel assembly 208.

In another embodiment, the one or more processors 106 of controller 102are configured to direct the reactor core measurement system 302 tomeasure one or more state variable values of the reactor core 202 at oneor more locations within the reactor core 202. For example, the one ormore processors 106 may transmit a command signal (not shown) to thecore measurement system 302 indicative of a core measurement initiationacquisition command. In turn, the core measurement system 302 maymeasure one or more state variable values of the reactor core 202 at oneor more locations within the reactor core 202. In another embodiment,following measurement of one or more state variable values at one ormore locations within the reactor core 202, the core measurement system302 may transmit a signal 305 indicative of one or more measured statevariable values (e.g., temperature, rate-of-change of temperature,pressure, rate-of-change of pressure and the like) to the one or moreprocessors 106 of controller 102.

In another embodiment, upon operation of the nuclear reactor core 202 ofthe reactor 101 over a time interval, the one or more processors 106 ofcontroller 102 may generate a measured reactor core parameterdistribution based on the one or more received measurement values fromcore measurement system 302 acquired at one or more locations within thecore 202 of the nuclear reactor 101. For example, the one or moreprocessors 106 of controller 102 may generate a measured power densitydistribution based on the one or more received measurement values fromcore measurement system 302 acquired at one or more locations within thecore 202 of the nuclear reactor 101. By way of another example, the oneor more processors 106 of controller 102 may generate a measured rate ofchange of power density distribution based on the one or more receivedmeasurement values from core measurement system 302 acquired at one ormore locations within the core 202 of the nuclear reactor 101. By way ofanother example, the one or more processors 106 of controller 102 maygenerate a measured reactivity distribution based on the one or morereceived measurement values from core measurement system 302 acquired atone or more locations within the core 202 of the nuclear reactor 101. Byway of another example, the one or more processors 106 of controller 102may generate a measured rate of change of reactivity distribution basedon the one or more received measurement values from core measurementsystem 302 acquired at one or more locations within the core 202 of thenuclear reactor 101. It is recognized herein that the various reactorcore parameter distributions may be calculated utilizing a variety ofknown parameter calculation techniques. For example, the calculation ofpower density profiles utilizing at least neutron flux measurementswithin a reactor core is described generally in J. Kenneth Shultis,“Determining axial fuel-rod power-density profiles from in-core neutronflux measurements,” Nuclear Instruments and Methods in Physics ResearchA, Vol. 547 pp. 663-678 (2005), which is incorporated herein byreference in the entirety.

In another embodiment, the one or more processors 106 of controller 102may generate a simulated operated core. In another embodiment, the oneor more processors 106 of controller 102 may generate a simulatedoperated core based at least on the initial loading distributionutilized when initiating operation of the reactor core 202. In thisregard, the initial loading distribution of the reactor core may serveas an input to a modeling routine suitable for generating a state of thesimulated core 120 after a given time of operation, with the simulatedoperated core remaining a selected state, such as an equilibrium state.In a further embodiment, the one or more processors 106 of controller102 may generate one or more reactor core parameter distributions of thesimulated operated nuclear reactor core. For instance, the one or moreprocessors 106 of controller 102 may generate a power densitydistribution for the simulated operated nuclear core utilizing at leastthe initial, or starting, loading distribution of the core 202 of thenuclear reactor 101. In another instance, the one or more processors 106of controller 102 may generate a power density rate-of-changedistribution for the simulated operated nuclear core utilizing at leastthe initial loading distribution of the core 202 of the nuclear reactor101. In another instance, the one or more processors 106 of controller102 may generate a reactivity distribution for the simulated operatednuclear core utilizing at least the initial loading distribution of thecore 202 of the nuclear reactor 101. In another instance, the one ormore processors 106 of controller 102 may generate a reactivityrate-of-change distribution for the simulated operated nuclear coreutilizing at least the initial loading distribution of the core 202 ofthe nuclear reactor 101. It is noted herein that any nuclear reactorcore modeling routine known in the art may be implemented in order tosimulate the evolution of the initially loaded reactor core 202 as afunction of operation time.

In another embodiment, following the generation of a measured reactorcore parameter distribution by the one or more processors 106 ofcontroller 102, the one or more processors 106 may compare the generatedmeasured reactor core parameter distribution acquired from the reactorcore 202 to one or more reactor core parameter distributions of thesimulated operated nuclear reactor core.

In another embodiment, the comparison of the generated measured reactorcore parameter distribution and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core mayinclude, but is not limited to, calculating a deviation metric betweenthe generated measured reactor core parameter distribution and the oneor more reactor core parameter distributions of the simulated operatednuclear reactor core. In one embodiment, the one or more processors 106may calculate at least one deviation metric between at least a portionof the generated measured reactor core parameter distribution and aportion of the one or more reactor core parameter distributions of thesimulated operated nuclear reactor core. It is noted herein that thedeviation metric calculated by the one or more processors 106 mayinclude any metric known in the art suitable for quantifying adifference or deviation between all or a portion of the generatedmeasured reactor core parameter and the one or more reactor coreparameter distributions of the simulated operated nuclear reactor core.For example, the deviation metric may include, but is not limited to, adifference (e.g., difference at a common position), a relativedifference, a ratio, an averaged difference (e.g., spatially averageddifference), maximum difference (e.g., maximum difference between anytwo or more common positions), minimum difference (e.g., minimumdifference between two or more common positions), aggregated deviation(e.g., global deviation metric) or any other deviation metric known inthe art.

It is recognized herein that both the generated measured reactor coreparameter distribution and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core may eachconsist of a three-dimensional distribution of a given reactor coreparameter throughout the given nuclear reactor core. As such, acomparison between the generated measured reactor core parameterdistribution and a portion of the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core may includeany comparison technique known in the art suitable for comparing two ormore three-dimensional varying distributions.

In one embodiment, the comparison may include comparing the generatedmeasured reactor core parameter distribution and the one or more reactorcore parameter distributions of the simulated operated nuclear reactorcore along a selected direction in the reactor core 202 and thesimulated operated core. For example, the comparison may includecomparing the reactor core parameter distributions along at leastsimilar radial lines running through the simulated operated core andreactor core 202. It is noted that a number of comparisons, each along adifferent direction, may be made between the simulated operated core andreactor core 202. Then, the multiple one-dimensional comparisons may beaggregated in order to provide a global deviation metric representativeof the overall deviation between the generated measured reactor coreparameter distribution and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core.

In another embodiment, the comparison may include comparing the reactorcore parameter distributions across a selected plane, or cross-section,in the simulated operated core and the reactor core 202. For example,the comparison may include comparing the reactor core parameterdistributions across at least similar cross-sections running through thesimulated operated core and the reactor core 202. It is further notedthat a number of comparisons, each at a different cross-section, may bemade between the simulated operated core and reactor core 202. Then, themultiple two-dimensional comparisons may be aggregated in order toprovide a global deviation metric representative of the overalldeviation between the generated measured reactor core parameterdistribution and the one or more reactor core parameter distributions ofthe simulated operated nuclear reactor core.

In another embodiment, the comparison may include comparingdistributions at each of a set of regions in the simulated operated coreand the reactor core 202. For example, the comparison may includegenerating an aggregated deviation metric between the generated measuredreactor core parameter distribution and the one or more reactor coreparameter distributions of the simulated operated nuclear reactor coreby calculating a deviation metric between the two distributions at eachof a sets of regions (e.g., a set of selected regions similar to regions122 of system 100). For example, the set of regions may correspond tothe fuel assemblies contained within the simulated operated core and thereactor core 202. By way of another example, the set of regions maycorrespond to portions (e.g., sub-assembly volumes (see FIG. 1K) orindividual fuel pins) of the fuel assemblies contained within thesimulated operated core and the reactor core 202. Then, deviationmetrics collected in the multiple comparisons from each region may bestatistically aggregated to provide a global deviation metricrepresentative of the overall deviation between the generated measuredreactor core parameter distribution and the one or more reactor coreparameter distributions of the simulated operated nuclear reactor core.In another embodiment, the comparison may include comparing averageddeviation values (e.g., averaged difference values) for one or morereactor core parameter distributions extracted from selected volumes(e.g., regions or groups of regions) of the simulated operated core andthe reactor core 202.

In another embodiment, the comparison of the generated measured reactorcore parameter distribution from the reactor core 202 and the one ormore reactor core parameter distributions of the simulated operatednuclear reactor core may include, but is not limited to, comparing agenerated measured reactor core power density distribution of thereactor core 202 to a reactor core power density distribution of asimulated operated nuclear reactor core. For example, followingoperation of the core 202 for a given time interval, the one or moreprocessors 106 of controller may generate a measured power densitydistribution using measurement results from core measurement system 302.The one or more processors 106 may further generate a power densitydistribution for the simulated operated nuclear reactor core utilizingthe initial loading distribution of the nuclear reactor core 202. Inturn, the one or more processors may compare (e.g., calculate adeviation metric) a portion of the power density distribution of thereactor core 202 to a portion of the power density distribution for thesimulated operated nuclear reactor core.

In another embodiment, the comparison of the generated measured reactorcore parameter distribution from the reactor core 202 and the one ormore reactor core parameter distributions of the simulated operatednuclear reactor core may include, but is not limited to, comparing agenerated measured reactor core rate-of-change of power densitydistribution of the reactor core 202 to a reactor core rate-of-changepower density distribution of a simulated operated nuclear reactor core.For example, following operation of the core 202 for a given timeinterval, the one or more processors 106 of controller may generate ameasured rate-of-change power density distribution using measurementresults from core measurement system 302. The one or more processors 106may further generate a rate-of-change power density distribution for thesimulated operated nuclear reactor core utilizing the initial loadingdistribution of the nuclear reactor core 202. In turn, the one or moreprocessors may compare a portion of the rate-of-change power densitydistribution of the reactor core 202 to a portion of the rate-of-changepower density distribution for the simulated operated nuclear reactorcore.

In another embodiment, the comparison of the generated measured reactorcore parameter distribution from the reactor core 202 and the one ormore reactor core parameter distributions of the simulated operatednuclear reactor core may include, but is not limited to, comparing agenerated measured reactor core reactivity distribution of the reactorcore 202 to a reactor core reactivity distribution of a simulatedoperated nuclear reactor core. For example, following operation of thecore 202 for a given time interval, the one or more processors 106 ofcontroller may generate a measured reactivity distribution usingmeasurement results from core measurement system 302. The one or moreprocessors 106 may further generate a reactivity distribution for thesimulated operated nuclear reactor core utilizing the initial loadingdistribution of the nuclear reactor core 202. In turn, the one or moreprocessors may compare (e.g., calculate a deviation metric) a portion ofthe reactivity distribution of the reactor core 202 to a portion of thereactivity distribution for the simulated operated nuclear reactor core.

In another embodiment, the comparison of the generated measured reactorcore parameter distribution from the reactor core 202 and the one ormore reactor core parameter distributions of the simulated operatednuclear reactor core may include, but is not limited to, comparing agenerated measured reactor core rate-of-change of reactivitydistribution of the reactor core 202 to a reactor core rate-of-changereactivity distribution of a simulated operated nuclear reactor core.For example, following operation of the core 202 for a given timeinterval, the one or more processors 106 of controller may generate ameasured rate-of-change reactivity distribution using measurementresults from core measurement system 302. The one or more processors 106may further generate a rate-of-change reactivity distribution for thesimulated operated nuclear reactor core utilizing the initial loadingdistribution of the nuclear reactor core 202. In turn, the one or moreprocessors may compare a portion of the rate-of-change reactivitydistribution of the reactor core 202 to a portion of the rate-of-changereactivity distribution for the simulated operated nuclear reactor core.

In another embodiment, the one or more processors 106 of controller 102may determine the state of operation compliance of the reactor core 202based on the deviation metric. For example, upon comparing the generatedmeasured reactor core parameter distribution and the one or more reactorcore parameter distributions of the simulated operated nuclear reactorcore, the one or more processors 106 of controller 102 may determinewhether the deviation metric calculated between the generated measuredreactor core parameter distribution and the one or more reactor coreparameter distributions of the simulated operated nuclear reactor coreis above, at or below a selected tolerance level. In one embodiment, adetermination that the deviation metric is at or below the selectedtolerance level may correspond with an “in-compliance” state for thenuclear reactor core 202. In another embodiment, a determination thatthe deviation metric is above the selected tolerance level maycorrespond with an “out-of-compliance” state for the nuclear reactorcore 202.

In another embodiment, in response to a determination of anout-of-compliance state, the one or more processors 106 of controller102 may determine an additional loading distribution of the core 202 ofthe nuclear reactor 101 via an additional core simulation process. It isfurther noted herein that the additional simulated loading distributionrepresents a loading distribution that may act to correct anout-of-compliance nuclear reactor core 202 such that re-arrangement ofthe reactor core 202 in a manner consistent with the additionalsimulated core serves to bring the core 202 into an in-compliance state.

In another embodiment, the additional simulation process executed by theone or more processors 106 of controller 102 is configured to determinea set of simulated positions of a set of regions within an additionalsimulated core suitable for reducing the deviation metric between atleast one reactor core parameter distribution of the additionalsimulated core and the received at least one reactor core parameterdistribution associated with a state (e.g., equilibrium state) of a coreof a reference nuclear reactor below a selected tolerance level. Theadditional simulated core and the additional nuclear fuel loadingdistribution making up the additional core may be determined utilizing amethodology similar to that described with respect to systems 100 and200 of the present disclosure. In one embodiment, the nuclear reactorcore 202 of system 300 is previously loaded with fuel assemblies 208. Assuch, the procedure utilized to determine the additional nuclear fuelloading distribution of the additional simulated core may includeutilizing the loading distribution of the nuclear reactor core 202 inits operated state (i.e., immediately prior to measurement viameasurement system 302) as an initial, or starting, loading distributionof the additional simulated core in the additional simulation process(e.g., see process 170 of FIG. 1P) carried out by the one or moreprocessors 106.

The fuel handler 204 may include any nuclear fuel assembly handler, ornuclear fuel assembly handling system, known in the art, as describedpreviously herein. For example, the nuclear fuel handler 204 may includeany nuclear fuel assembly handler/handling system capable of gripping afuel assembly and moving the fuel assembly from an initial location to anew location.

In one embodiment, responsive to the initial loading distributiondetermination, the fuel handler 204 may arrange at least one fuelassembly 208 of the core 202 of the nuclear reactor 101 according to theset of simulated positions of the set of regions of the simulated BOCnuclear reactor core 120. The description of the fuel handler 204, fuelhandler controller 206 and arrangement of the fuel assemblies 208 ofcore 202 according to an initial loading distribution has been describedpreviously herein and should be interpreted to extend to system 300.

In another embodiment, the fuel handler 204 is further configured toarrange one or more fuel assemblies of the reactor core 202 according tothe set of simulated positions of a set of regions within the additionalsimulated core, responsive to the additional loading distributiondetermination. In one embodiment, as shown in FIG. 3A, the one or moreprocessors 106 of controller 102 are configured to transmit one or moresignals 307 indicative of the set of positions of a set of regions of anadditional simulated core generated by controller 102 to the fuelhandler controller 206. In turn, the fuel handler controller 206 mayreceive the one or more signals 307 from controller 102 and direct thefuel handler 204 (e.g., via signal 309) to arrange the one or more fuelassemblies 208 of the reactor core 202 in accordance with the set ofpositions of the set of regions of the additional simulated core encodedin the transmitted signal. In this regard, upon generating an additionalloading distribution, the controller 102 may direct the fuel handler 204to arrange the constituents of the core 202 such that they match theadditional loading distribution generated by controller 102.

In another embodiment, the one or more processors 106 of controller 102are configured to transmit one or more signals (not shown) indicative ofa set of positions of the set of regions of the additional simulatedcore generated by controller 102 to the control system 180 of thenuclear reactor 101. In turn, the control system 180 of the nuclearreactor 101 may receive the one or more signals from controller 102 anddirect the fuel handler 204 to arrange the one or more fuel assemblies208 of the reactor core 202 in accordance with the set of positions ofthe set of regions of the additional simulated core encoded in thetransmitted signal.

In another embodiment, the one or more processors 106 of controller 102are configured to transmit one or more signals (not shown) indicative ofthe set of positions of the set of regions of the additional simulatedcore generated by controller 102 directly to the fuel handler 204. Inthis manner, the one or more processors 106 of controller 102 may directthe fuel handler 204 to arrange the one or more fuel assemblies 208 ofthe reactor core 202 in accordance with the set of positions of the setof regions of the additional simulated core encoded in the transmittedsignal.

In another embodiment, the one or more processors 106 of controller 102are configured to direct the fuel handler 204 to translate one or morefuel assemblies 208 of the core 202 of the nuclear reactor 101 from aninitial location to a subsequent location according to the set ofpositions of the set of regions of the additional simulated core. Inthis regard, the fuel handler 204 (or multiple fuel handlers) mayarrange (or re-arrange) all or a portion of the fuel assemblies 208 ofthe of the core 202 of the nuclear reactor 101 according to the set ofpositions of the set of regions of the additional simulated coregenerated by the controller 102.

In another embodiment, the one or more processors 106 of controller 102are configured to direct the fuel handler 204 to replace one or morefuel assemblies 208 of the core 202 of the nuclear reactor 101 accordingto the set of positions of the set of regions of the additionalsimulated core. In this regard, the fuel handler 204 (or multiple fuelhandlers) may replace all or a portion of the fuel assemblies 208 of thecore 202 of the nuclear reactor 101 according to the set of positions ofthe set of regions of the additional simulated core generated by thecontroller 102.

In another embodiment, as described previously herein, the fuel handler204 may be controlled via user input. For example, in response to thegenerated additional loading distribution of the additional simulatedcore, the user may choose to accept, reject or modify the displayedadditional loading distribution. For instance, upon being presented withan additional loading distribution, the user may approve the additionalloading distribution via the user input device 118. In turn, the one ormore processors 106 of controller 102 may direct the fuel handler 204 toimplement the approved additional loading distribution, as describedthroughout the present disclosure. In another instance, upon beingpresented with an undesired additional loading distribution, the usermay reject the undesired additional loading distribution via the userinput device 118. In turn, the one or more processors 106 of controller102 may terminate or repeat the additional simulated coresimulation/handling procedure of the present invention. In anotherinstance, upon being presented with an undesired additional loadingdistribution, the user may modify the undesired additional loadingdistribution via the user input device 118. For example, the user mayaccept a portion of the provided additional loading distribution, whilealtering one or more other portions of the additional loadingdistribution. For instance, the user may alter, or re-arrange (e.g., viauser input device 118 and/or display 116), the arrangement of the fuelassemblies or fuel assembly ensembles of the additional nuclear fuelloading distribution provided by controller 102. In turn, the one ormore processors 106 of controller 102 may direct the fuel handler 204 toimplement the user-altered additional nuclear fuel loading distribution.

In another embodiment, the one or more processors 106 of controller 102may report the operation compliance state (e.g., an in-compliance stateor an out-of-compliance) to one or more associated devices or systems.In one embodiment, the one or more processors 106 of controller 102 mayreport the operational compliance state to a display device 116. Inanother embodiment, the one or more processors 106 of controller 102 mayreport the operational compliance state to one or more memory devices.For example, the one or more processors 106 may transmit the operationalcompliance state to a database 107 maintained in memory 108 ofcontroller 102. By way of another example, the one or more processors106 may transmit the operational compliance state to a databasemaintained in memory of a remote system (e.g., remote server)communicatively coupled to controller 102. In another embodiment, theone or more processors 106 of controller 102 may report the operationcompliance state of the reactor core 202 to an operation system ofnuclear reactor 101. For example, the one or more processors 106 ofcontroller 102 may transmit the operational compliance state of thenuclear reactor core 202 to a control system 180 of the nuclear reactor101. By way of another example, the one or more processors 106 ofcontroller 102 may transmit the operational compliance state of thenuclear reactor core 202 to a safety system (not shown) of the nuclearreactor 101.

FIG. 3D illustrates a process flow diagram 320 of an example operationof system 300, in accordance with one or more embodiments of the presentinvention. In step 322, one or more processors 106 of controller 102 maygenerate an initial, or starting, nuclear fuel loading distributionusing a BOC simulation process suitable for generating a simulated BOCcore (e.g., simulated BOC core 120). For example, as describedthroughout the present disclosure, the one or more processors 106 ofcontroller 102 may generate a starting nuclear fuel loading distributionfor reactor core 202 based on a received reactor core parameterdistribution associated with a selected state (e.g., equilibrium state)of core of a reference nuclear reactor core. For instance, the one ormore processors 106 of controller 102 may generate a starting nuclearfuel loading distribution formed from “fresh” nuclear fuel based on areceived reactor core parameter distribution associated with anequilibrium state of a core of a reference nuclear reactor core at leastpartially formed from burned nuclear fuel.

In step 324, one or more processors 106 of controller 102 may arrangeone or more fuel assemblies of the reactor core 202 of nuclear reactor101 according to the initial loading distribution generated for thesimulated BOC core in step 322. For example, one or more processors 106of controller 102 may arrange one or more fuel assemblies of the reactorcore 202 of nuclear reactor 101 according to a set of simulatedpositions of a set of regions of the simulated BOC nuclear reactor core.

In step 326, the nuclear core 202 of the nuclear reactor 101 is operatedfor a selected time interval. In step 328, the reactor core measurementsystem 302 may measure one or more values of a selected reactor coreparameter at one or more locations within the nuclear reactor core 202of reactor 101. For example, the reactor core measurement system 302 maymeasure a value of one or more selected state variables of the nuclearreactor core 202 at one or more locations within the nuclear reactorcore 202 of reactor 101. For instance, the reactor core measurementsystem 302 may measure the temperature or rate-of-change of temperatureof the nuclear reactor core 202 at one or more locations within thenuclear reactor core 202 of reactor 101. In another instance, thereactor core measurement system 302 may measure the pressure orrate-of-change of pressure of the nuclear reactor core 202 at one ormore locations within the nuclear reactor core 202 of reactor 101. Inanother instance, the reactor core measurement system 302 may measurethe neutron flux or rate-of-change of neutron flux of the nuclearreactor core 202 at one or more locations within the nuclear reactorcore 202 of reactor 101.

In step 330, the one or more processors 106 of controller 102 maygenerate a measured reactor core parameter distribution utilizing themeasurements from the reactor core measurement system 302. For example,the one or more processors 106 of controller 102 may generate a measuredreactor core parameter distribution utilizing a set of state variablevalues acquired at multiple locations within the nuclear reactor core202 by the reactor core measurement system 302. For instance, the one ormore processors 106 of controller 102 may generate a measured powerdensity distribution utilizing a set of temperature, pressure and/orneutron flux values acquired at multiple locations within the nuclearreactor core 202 by the reactor core measurement system 302.

In step 332, the one or more processors 106 of controller 102 maygenerate a reactor core parameter distribution for a simulated operatednuclear core. For example, the one or more processors 106 of controller102 may generate a reactor core parameter distribution for a simulatedoperated nuclear core utilizing at least the initial, or starting,loading distribution of the core 202 of the nuclear reactor 101. Forinstance, the one or more processors 106 of controller 102 may generatea power density distribution for a simulated operated nuclear coreutilizing at least the initial, or starting, loading distribution of thecore 202 of the nuclear reactor 101.

In step 334, the one or more processors 106 compare the generatedmeasured reactor core parameter distribution of step 330 to one or morereactor core parameter distributions of a simulated operated nuclearreactor core of step 332. For example, the one or more processors 106may generate a deviation metric between the generated measured reactorcore parameter distribution of step 330 and the one or more reactor coreparameter distributions of a simulated operated nuclear reactor core ofstep 332.

In step 336, the one or more processors 106 may determine the operationcompliance state of the nuclear reactor core 202 of reactor 101 usingthe comparison of the generated measured reactor core parameterdistribution to one or more reactor core parameter distributions of asimulated operated nuclear reactor core. In one embodiment, a deviationmetric between the generated measured reactor core parameterdistribution and the one or more reactor core parameter distributions ofthe simulated operated nuclear reactor core below (or at) a selectedtolerance level corresponds to an in-compliance state. In anotherembodiment, a deviation metric between the generated measured reactorcore parameter distribution and the one or more reactor core parameterdistributions of the simulated operated nuclear reactor core above aselected tolerance level corresponds to an out-of-compliance state. Inthe event the reactor core is in an in-compliance state, the process 320ends or moves back to step 326 to repeat the core measurement andanalysis steps 326-336. In the event the reactor core 202 is in anout-of-compliance state, the process 320 moves to step 338.

In step 338, after identifying a state of out-of-compliance for reactorcore 202, the one or more processors 106 of controller 102 may generatean additional loading distribution of the core 202. In one embodiment,the additional simulation process executed by the one or more processors106 of controller 102 is configured to determine a set of simulatedpositions of a set of regions within an additional simulated coresuitable for reducing a deviation metric between at least one reactorcore parameter distribution of the additional simulated core and thereceived at least one reactor core parameter distribution (received instep 322) associated with a state (e.g., equilibrium state) of a core ofa reference nuclear reactor below a selected tolerance level.

In step 340, after generating the additional loading distribution instep 338, the fuel handler 204 may arrange one or more fuel assemblies208 of the reactor core 202 according to the set of simulated positionsof a set of regions within the additional simulated core. Afterarrangement of the fuel assemblies 208 of the reactor core 202, theprocess 320 ends or moves back to step 326 to repeat the coremeasurement and analysis steps 326-336. It is recognized that thisprocess may be repeated indefinitely in order to maintain the reactorcore 202 in a state of compliance.

The one or more processors 106 of the controller 102 may becommunicatively coupled to the various sub-systems (e.g., coredistribution source 103, controller of reactor 180, fuel handler 2 s 04,fuel handler controller 206, reactor core measurement system 302 and thelike)) of systems 100, 200 and 300 in any manner known in the art. Forexample, the one or more processors 106 may be communicatively coupledto the core measurement system 302 via a wireline (e.g., copper wire,fiber optic cable, and the like) or wireless connection (e.g., RFcoupling). By way of another example, the one or more processors 106 maybe communicatively coupled to the control system 180 of the reactor 101via a wireline or wireless connection. In another example, the one ormore processors 106 may be communicatively coupled to a remote system(not shown), such as a remote computer system or a control system of aremote nuclear reactor, via a wireline or wireless connection. Inanother example, the one or more processors 106 may be communicativelycoupled to any sub-system via a network. In this regard, the controller102 may include a network interface device (not shown) suitable forinterfacing with a network, while a sub-system includes a networkinterface device also suitable for interfacing with the network. Thenetwork interface devices may include any network interface device knownin the art. For instance, the network interface devices may include awireline-based interface device (e.g., DSL-based interconnection,Cable-based interconnection, T9-based interconnection, and the like). Inanother instance, the network interface devices may include awireless-based interface device employing GSM, GPRS, CDMA, EV-DO, EDGE,WiMAX, LTE, Wi-Fi protocols, and the like.

Following are a series of flowcharts depicting implementations. For easeof understanding, the flowcharts are organized such that the initialflowcharts present implementations via an example implementation andthereafter the following flowcharts present alternate implementationsand/or expansions of the initial flowchart(s) as either sub-componentoperations or additional component operations building on one or moreearlier-presented flowcharts. Those having skill in the art willappreciate that the style of presentation utilized herein (e.g.,beginning with a presentation of a flowchart(s) presenting an exampleimplementation and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations. In addition, thoseskilled in the art will further appreciate that the style ofpresentation used herein also lends itself well to modular and/orobject-oriented program design paradigms.

FIG. 4A illustrates an operational flow 400 representing exampleoperations related to generating a nuclear reactor core loadingdistribution. In FIG. 4A and in following figures that include variousexamples of operational flows, discussion and explanation may beprovided with respect to the above-described examples of FIGS. 1Athrough 1P, and/or with respect to other examples and contexts. However,it should be understood that the operational flows may be executed in anumber of other environments and contexts, and/or in modified versionsof FIGS. 1A through 1P. Also, although the various operational flows arepresented in the sequence(s) illustrated, it should be understood thatthe various operations may be performed in other orders than those whichare illustrated, or may be performed concurrently.

After a start operation, the operational flow 400 moves to a receivingoperation 410. The receiving operation 410 depicts receiving at leastone reactor core parameter distribution 103 associated with a state of acore of a nuclear reactor. For example, as shown in FIGS. 1A through 1P,one or more processors 106 of the controller 102 are communicativelycoupled to a core parameter distribution source 104 and configured toreceive one or more reactor core parameter distributions 103 of a coreof a nuclear reactor (e.g., reference nuclear reactor) in a given state(e.g., equilibrium state, a state approaching equilibrium, or a state ofequilibrium onset) from the core parameter distribution source 104(e.g., memory). For instance, the core parameter distribution source 104may include, but is not limited to, one or more memory devicesconfigured to store and/or maintain one or more reactor core parameterdistributions 103 (e.g., measured reactor core parameter distribution orsimulated reactor core parameter distribution). Further, the one or moreprocessors 106 of the controller 102 may receive a reactor coreparameter distribution for a core of the nuclear reactor in a givenstate in the form of a database or map (e.g., two-dimensional orthree-dimensional map) indicative of the reactor core parameter as afunction of position within the core of the nuclear reactor.

Then, generating operation 420 depicts generating an initial fuelloading distribution for a simulated BOC core of the nuclear reactor.For example, as shown in FIGS. 1A through 1P, one or more processors 106of the controller 102 may generate an initial fuel loading distributionfor a simulated BOC core of the nuclear reactor.

Then, selecting operation 430 depicts selecting an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor. For example, as shown in FIGS. 1A through 1P,the one or more processors 106 of the controller 102 may select aninitial set of positions associated with a set of regions 122 within thesimulated BOC core 120 of the nuclear reactor.

Then, generating operation 440 depicts generating an initial set of fueldesign parameter values utilizing at least one design variable of eachof the set of regions. For example, as shown in FIGS. 1A through 1P, theone or more processors 106 of the controller 102 may generate an initialset of fuel design parameter values utilizing at least one designvariable of each of the set of regions.

Then, calculating operation 450 depicts calculating at least one reactorcore parameter distribution of the simulated BOC core utilizing thegenerated initial set of fuel design parameter values associated withthe set of regions located at the initial set of positions of thesimulated BOC core. For example, as shown in FIGS. 1A through 1P, theone or more processors 106 of the controller 102 may calculate one ormore reactor core parameter distributions of the simulated BOC coreutilizing the generated initial set of fuel design parameter valuesassociated with the set of regions located at the initial set ofpositions of the simulated BOC core.

Then, loading distribution generating step 460 depicts generating aloading distribution by performing at least one perturbation process onthe set of regions of the simulated BOC core in order to determine asubsequent set of positions for the set of regions within the simulatedBOC core. For example, as shown in FIGS. 1A through 1P, the one or moreprocessors 106 of the controller 102 may generate a loading distributionby performing one or more perturbation processes on the set of regions122 of the simulated BOC 120 core in order to determine a subsequent setof positions for the set of regions within the simulated BOC core. Forinstance, as shown in FIG. 1P, the perturbation procedure 170 mayiteratively vary the positions of the regions 122 within the simulatedcore 120 until a suitable loading distribution of the simulated BOC core120 is achieved.

FIG. 4B illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 4B illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include operation 412.

The operation 412 illustrates receiving at least one reactor coreparameter distribution associated with an equilibrium state of a core ofa nuclear reactor. For example, as shown in FIGS. 1A through 1P, one ormore processors 106 of controller 102 may receive one or more reactorcore parameter distributions 103 for a core of a nuclear reactor in anequilibrium state from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a nuclear reactor in anequilibrium state. Then, the one or more processors 106 of controller102 may retrieve the reactor core parameter distribution 103 for a coreof a nuclear reactor in an equilibrium state stored in the coreparameter distribution source 104.

By way of another example, as shown in FIGS. 1A through 1P, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor in a stateapproaching equilibrium from a core parameter distribution source 104.In this regard, the core parameter distribution source 104 may store areactor core parameter distribution for a core of a nuclear reactor in astate approaching equilibrium. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactor core parameter distribution 103for a core of a nuclear reactor in a state approaching equilibriumstored in the core parameter distribution source 104.

By way of another example, as shown in FIGS. 1A through 1P, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor at an onsetof an equilibrium state from a core parameter distribution source 104.In this regard, the core parameter distribution source 104 may store areactor core parameter distribution for a core of a nuclear reactor atan onset of an equilibrium state. Then, the one or more processors 106of controller 102 may retrieve the reactor core parameter distribution103 for a core of a nuclear reactor at an onset of an equilibrium statestored in the core parameter distribution source 104.

FIG. 5 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 5 illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include operations 502 and/or 504.

The operation 502 illustrates receiving at least one reactor coreparameter distribution associated with a state of a core of a thermalnuclear reactor. For example, as shown in FIGS. 1A through 1P, one ormore processors 106 of controller 102 may receive one or more reactorcore parameter distributions 103 for a core of a thermal nuclear reactorfrom a core parameter distribution source 104. In this regard, the coreparameter distribution source 104 may store a reactor core parameterdistribution for a core of a reference thermal nuclear reactor. Then,the one or more processors 106 of controller 102 may retrieve thereactor core parameter distribution 103 for a core of the referencethermal nuclear reactor stored in the core parameter distribution source104.

In another embodiment, the operation 504 illustrates receiving at leastone reactor core parameter distribution associated with a state of acore of a fast nuclear reactor. For example, as shown in FIGS. 1Athrough 1P, one or more processors 106 of controller 102 may receive oneor more reactor core parameter distributions 103 for a core of a fastnuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a reference fast nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactor core parameter distribution 103 for a core of thereference fast nuclear reactor stored in the core parameter distributionsource 104.

FIG. 6 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 6 illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include an operation 602, and/or operation604.

In one embodiment, operation 602 illustrates receiving at least onereactor core parameter distribution associated with a state of a core ofa breed-and-burn nuclear reactor. For example, as shown in FIGS. 1Athrough 1P, one or more processors 106 of controller 102 may receive oneor more reactor core parameter distributions 103 for a core of abreed-and-burn nuclear reactor from a core parameter distribution source104. In this regard, the core parameter distribution source 104 maystore a reactor core parameter distribution for a core of a referencebreed-and-burn nuclear reactor. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactor core parameter distribution 103for a core of the reference breed-and-burn nuclear reactor stored in thecore parameter distribution source 104.

In another embodiment, operation 604 illustrates receiving at least onereactor core parameter distribution associated with a state of a core ofa traveling wave reactor. For example, as shown in FIGS. 1A through 1P,one or more processors 106 of controller 102 may receive one or morereactor core parameter distributions 103 for a core of a traveling wavenuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a reference traveling nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactor core parameter distribution 103 for a core of thereference traveling wave nuclear reactor stored in the core parameterdistribution source 104.

FIG. 7 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 7 illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include an operation 702 and/or operation 704.

In one embodiment, the operation 702 illustrates receiving at least onereactor core parameter distribution associated with a state of a core ofa nuclear reactor, the core including at least one fuel assembly. Forexample, as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may receive one or more reactor core parameterdistributions 103 for a core of a nuclear reactor including one or morefuel assemblies from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a nuclear reactor with one ormore fuel assemblies. Then, the one or more processors 106 of controller102 may retrieve the reactor core parameter distribution 103 for a coreof a nuclear reactor with one or more fuel assemblies stored in the coreparameter distribution source 104.

Further, operation 704 illustrates receiving at least one reactor coreparameter distribution associated with a state of a core of a nuclearreactor, the core including at least one fuel assembly including atleast one pin. For example, as shown in FIGS. 1A through 1P, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor includingone or more fuel assemblies with one or more fuel pins from a coreparameter distribution source 104. In this regard, the core parameterdistribution source 104 may store a reactor core parameter distributionfor a core of a nuclear reactor with one or more fuel assemblies havingone or more fuel pins. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactor core parameter distribution 103for a core of a nuclear reactor with one or more fuel assemblies havingone or more fuel pins stored in the core parameter distribution source104.

FIG. 8 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 8 illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include an operation 802 and/or operation 804.

The operation 802 illustrates receiving a power density distributionassociated with a state of a core of a nuclear reactor. For example, asshown in FIGS. 1A through 1P, one or more processors 106 of controller102 may receive one or more power density distributions for a givenstate of a core of a nuclear reactor from a core parameter distributionsource 104. In this regard, the core parameter distribution source 104may store a power density distribution for a given state of a core of anuclear reactor. Then, the one or more processors 106 of controller 102may retrieve the power density distribution for a given state of a coreof a nuclear reactor stored in the core parameter distribution source104. Further, the one or more processors 106 of the controller 102 mayreceive a power density distribution for a core of the nuclear reactorin the form of a database or map (e.g., two-dimensional orthree-dimensional map) indicative of the power generation density as afunction of position within the core of the nuclear reactor.

In another embodiment, operation 804 illustrates receiving a rate ofchange of a power density distribution associated with a state of a coreof a nuclear reactor. For example, as shown in FIGS. 1A through 1P, oneor more processors 106 of controller 102 may receive one or more powerdensity rate-of-change distributions for a given state of a core of anuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a powerdensity rate-of-change distribution for a given state of core of anuclear reactor. Then, the one or more processors 106 of controller 102may retrieve the power density rate-of-change distribution for a givenstate of a core of a nuclear reactor stored in the core parameterdistribution source 104. Further, the one or more processors 106 of thecontroller 102 may receive a power density rate-of-change distributionfor a core of the nuclear reactor in the form of a database or map(e.g., two-dimensional or three-dimensional map) indicative of the rateof change of power generation density as a function of position withinthe core of the nuclear reactor.

FIG. 9 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 9 illustrates example embodiments where thereceiving operation 410 may include at least one additional operation.Additional operations may include an operation 902, 904 and/or operation906.

The operation 902 illustrates receiving a reactivity distributionassociated with a state of a core of a nuclear reactor. For example, asshown in FIGS. 1A through 1P, one or more processors 106 of controller102 may receive one or more reactivity distributions for a given stateof a core of a nuclear reactor from a core parameter distribution source104. In this regard, the core parameter distribution source 104 maystore a reactivity distribution for a given state of a core of a nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactivity distribution for a given state of a core of anuclear reactor stored in the core parameter distribution source 104.Further, the one or more processors 106 of the controller 102 mayreceive a reactivity distribution for a core of the nuclear reactor inthe form of a database or map (e.g., two-dimensional orthree-dimensional map) indicative of reactivity as a function ofposition within the core of the nuclear reactor.

In another embodiment, the operation 904 illustrates receiving a rate ofchange of a reactivity distribution associated with a state of a core ofa nuclear reactor. For example, as shown in FIGS. 1A through 1P, one ormore processors 106 of controller 102 may receive one or more reactivityrate-of-change distributions for a given state of a core of a nuclearreactor from a core parameter distribution source 104. In this regard,the core parameter distribution source 104 may store a reactivityrate-of-change distribution for a given state of a core of a nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactivity rate-of-change distribution for a given state ofa core of a nuclear reactor stored in the core parameter distributionsource 104. Further, the one or more processors 106 of the controller102 may receive a reactivity rate-of-change distribution for a core ofthe nuclear reactor in the form of a database or map (e.g.,two-dimensional or three-dimensional map) indicative of the rate ofchange of reactivity as a function of position within the core of thenuclear reactor.

In another embodiment, the operation 906 illustrates receiving at leastone reactor core parameter distribution associated with a state of acore of a nuclear reactor, the core including plutonium. For example, asshown in FIGS. 1A through 1P, one or more processors 106 of controller102 may receive one or more reactor core parameter distributions for agiven state of a nuclear reactor core including plutonium from a coreparameter distribution source 104. In this regard, the core parameterdistribution source 104 may store a reactor core parameter distributionfor a given state of a nuclear reactor core including plutonium. Then,the one or more processors 106 of controller 102 may retrieve thereactor core parameter distribution for a given state of a nuclearreactor core including plutonium stored in the core parameterdistribution source 104.

FIG. 10 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 10 illustrates example embodiments where thereference generating operation 420 may include at least one additionaloperation. Additional operations may include an operation 1002 and/oroperation 1004.

The operation 1002 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor, at least aportion of the BOC core including recycled nuclear fuel. For example, asshown in FIGS. 1A through 1P, the one or more processors 106 of thecontroller 102 may generate an initial fuel loading distribution for asimulated BOC core of the nuclear reactor including recycled nuclearfuel. For instance, the one or more processors 106 of the controller 102may provide the spatial distribution of nuclear fuel (including fissileand non-fissile material) throughout a simulated BOC core (e.g.,throughout the fuel assemblies of a simulated BOC core) including atleast some recycled nuclear fuel (e.g., recycled uranium).

In another embodiment, operation 1004 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, at least a portion of the BOC core including unburned nuclearfuel. For example, as shown in FIGS. 1A through 1P, the one or moreprocessors 106 of the controller 102 may generate an initial fuelloading distribution for a simulated BOC core of the nuclear reactorincluding recycled nuclear fuel. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel (including fissile and non-fissilematerial) throughout a simulated BOC core including at least someunburned nuclear fuel (e.g., unburned uranium).

FIG. 11 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 11 illustrates example embodiments where thegenerating operation 420 may include at least one additional operation.Additional operations may include an operation 1102 and/or operation1104.

The operation 1102 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor, at least aportion of the BOC core including enriched nuclear fuel. For example, asshown in FIGS. 1A through 1P, the one or more processors 106 of thecontroller 102 may generate an initial fuel loading distribution for asimulated BOC core of the nuclear reactor including enriched nuclearfuel. For instance, the one or more processors 106 of the controller 102may provide the spatial distribution of nuclear fuel (including fissileand non-fissile material) throughout a simulated BOC core including atleast some enriched nuclear fuel.

In another embodiment, operation 1104 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, at least a portion of the BOC core including enriched uraniumbased nuclear fuel. For example, as shown in FIGS. 1A through 1P, theone or more processors 106 of the controller 102 may generate an initialfuel loading distribution for a simulated BOC core of the nuclearreactor including enriched uranium. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel (including fissile and non-fissilematerial) throughout a simulated BOC core including at least someenriched uranium.

FIG. 12 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 12 illustrates example embodiments where thereference generating operation 420 may include at least one additionaloperation. Additional operations may include an operation 1202 and/oroperation 1204.

The operation 1202 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor via atleast one of user input and a controller. For example, as shown in FIGS.1A through 1P, the one or more processors 106 of the controller 102 maygenerate an initial fuel loading distribution for a simulated BOC coreof the nuclear reactor using at least one of user input and thecontroller 102. For instance, the one or more processors 106 of thecontroller 102 may provide the spatial distribution of nuclear fuel(including fissile and non-fissile material) throughout a simulated BOCcore utilizing a preprogrammed predictive algorithm executed by the oneor more processors 106 of the controller 102. In this regard, thepredictive algorithm may select the preferred initial fuel loadingdistribution based on a variety parameters, such as, but not limited to,historical data correlating initial fuel loading distribution startingpoints and quality of final fuel loading distribution, user selectedinitial fuel loading distribution preferences and the like.

In another instance, the one or more processors 106 of the controller102 may provide the spatial distribution of nuclear fuel (includingfissile and non-fissile material) throughout a simulated BOC coreutilizing user inputted data in conjunction with the controller 102. Inthis regard, the user may select an initial fuel loading distributionbased on a number of options presented to the user of the user display116. For example, the controller 102 may present the user (e.g., presenton display 116) with a plurality of initial fuel loading distributionsbased on an output of a preprogrammed predictive algorithm. Based onthis presentation of loading distributions on display 116, the user mayselect the preferred initial loading distribution using a user inputdevice 118.

In yet another instance, the one or more processors 106 of thecontroller 102 may provide the spatial distribution of nuclear fuel(including fissile and non-fissile material) throughout a simulated BOCcore based primarily on user inputted data. In this regard, the user mayselect or input an initial fuel loading distribution into the controller102. For example, a user may select the initial fuel loadingdistribution by choosing the specific material or materials (fissile ornon-fissile) for each fuel assembly or each pin of each fuel assemblyacross the simulated BOC core. Further, the user may make this initialfuel selection utilizing a graphical user interface 114 (e.g.,display/mouse, touchscreen, display/keyboard and the like), allowing theuser to select from a list of possible nuclear fuel materials (e.g.,fissile or non-fissile materials) at each of the simulated fuelassemblies or pins of each of the simulated fuel assemblies throughoutthe simulated BOC core. In this manner, the user, in a discretizedmanner, may build up the initial nuclear fuel loading distributionacross the simulated BOC core (e.g., built up with fuel assembly-levelresolution or built up with pin-level resolution). The selected initialloading distribution may then be read into the memory 108 of thecontroller 102 and used by the one or more processors 106 in subsequentsteps of the present invention.

In another embodiment, operation 1204 illustrates generating an initialfuel loading distribution for a simulated beginning-of-life (BOL) coreof the nuclear reactor. For example, as shown in FIGS. 1A through 1P,the one or more processors 106 of the controller 102 may generate aninitial fuel loading distribution for a simulated beginning-of-life(BOL) core of the nuclear reactor. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel (including fissile and non-fissilematerial) throughout a simulated BOL core (e.g., throughout the fuelassemblies of a simulated BOL core) of the nuclear reactor.

FIG. 13 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 13 illustrates example embodiments where thegenerating operation 420 may include at least one additional operation.Additional operations may include an operation 1302 and/or operation1304.

The operation 1302 illustrates randomly generating an initial fuelloading distribution for a simulated BOC core of the nuclear reactor.For example, as shown in FIGS. 1A through 1P, the one or more processors106 of the controller 102 may randomly generate an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor. Forinstance, the one or more processors 106 of the controller 102 may applya preprogrammed algorithm configured to randomly select the spatialdistribution of nuclear fuel (including fissile and non-fissilematerial) across the simulated BOC core.

In another embodiment, operation 1304 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, the simulated BOC core of the nuclear reactor including aplurality of simulated fuel assemblies. For example, as shown in FIGS.1A through 1P, the one or more processors 106 of the controller 102 maygenerate an initial fuel loading distribution through a plurality ofsimulated fuel assemblies for a simulated BOC core of the nuclearreactor. For instance, the one or more processors 106 of the controller102 may provide the spatial distribution of nuclear fuel (includingfissile and non-fissile material) throughout simulated BOC core byproviding the type and quantity of material within each of the fuelassemblies throughout the simulated BOC core. Further, the initial fuelloading distribution may be resolved at the pin-level of each fuelassembly of the simulated BOC core. In this regard, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel (including fissile and non-fissilematerial) throughout the BOC core by providing the type and quantify ofmaterial within each fuel pin of each fuel assembly throughout thesimulated BOC core.

FIG. 14 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 14 illustrates example embodiments where theselecting operation 430 may include at least one additional operation.Additional operations may include an operation 1402, 1404 and/oroperation 1406.

The operation 1402 illustrates selecting an initial set of positionsassociated with a set of regions within the simulated BOC core of thenuclear reactor, each of the initial set of positions corresponding toone of the set of regions. For example, as shown in FIGS. 1A through 1P,one or more processors 106 of controller 102 may select an initial setof positions (e.g., x, y, z positions) associated with a set of regionswithin the simulated BOC core of the nuclear reactor. Further, the oneor more processors 106 of the controller 102 may assign a relativeposition to each of a set of regions 122 within the simulated BOC core120 of the nuclear reactor. In this regard, each region as delineated bythe controller 102 may encompass a selected volume (e.g., selected bycontroller 102 or selected via user input) of the nuclear fuel withinthe simulated BOC core 120.

In another embodiment, the operation 1404 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set regions, each regionencompassing at least one fuel assembly. For example, as shown in FIGS.1A through 1P, one or more processors 106 of controller 102 may selectan initial set of positions (e.g., x, y, z positions) associated with aset of regions 122 within the simulated BOC core 120 of the nuclearreactor, whereby each region encompasses one or more fuel assemblies 124of the simulated BOC core 120. Further, the one or more processors 106of the controller 102 may assign a relative position to each regionencompassing one or more fuel assemblies 124 within the simulated BOCcore 120 of the nuclear reactor. For instance, as shown in FIG. 1I, theone or more processors 106 of the controller 102 are configured toselect an initial set of positions 140 of the set of regions 122,whereby each region 122 encompasses a single fuel assembly 124 of theBOC core 120. In another instance, as shown in FIG. 1J, the one or moreprocessors 106 of the controller 102 are configured to select an initialset of positions 140 of the set of regions 122, whereby each region 122encompasses multiple fuel assemblies 124 of the BOC core 120.

In another embodiment, the operation 1406 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set of regions, each of the set ofregions being a three dimensional region having a selected volume. Forexample, as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may select an initial set of positions 140 associatedwith a set of regions 122 within the simulated BOC core 120 of thenuclear reactor, whereby each region is a three dimensional regionhaving a selected volume. Further, the one or more processors 106 of thecontroller 102 may assign a relative position to each three dimensionalregion of selected volume within the simulated BOC core 120 of thenuclear reactor.

FIG. 15 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 15 illustrates example embodiments where theselecting operation 430 may include at least one additional operation.Additional operations may include an operation 1502 and/or operation1504.

In another embodiment, the operation 1502 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set of regions, each of the set ofregions being a three dimensional region having a selected shape. Forexample, as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may select an initial set of positions 140 associatedwith a set of regions 122 within the simulated BOC core 120 of thenuclear reactor, whereby each region is a three dimensional regionhaving a selected shape (e.g., hexagonoid, cuboid, cylinder, ellipsoid,sphere, disc, ring and the like). Further, the one or more processors106 of the controller 102 may assign a relative position to each threedimensional region of selected shape within the simulated BOC core 120of the nuclear reactor.

In another embodiment, the operation 1504 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set of regions, the set of regionsincluding a selected number of regions. For example, as shown in FIGS.1A through 1P, one or more processors 106 of controller 102 may selectan initial set of positions 140 associated with a set of regions 122including a selected number of regions. Further, the one or moreprocessors 106 of the controller 102 may assign a relative position toeach region of the selected number of regions within the simulated BOCcore 120 of the nuclear reactor.

FIG. 16 illustrates alternative embodiments of the example operationalflow 400 of FIG. 16. FIG. 16 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 1602, 1604 and/oroperation 1606.

The operation 1602 illustrates generating an initial set of fuel designparameter values utilizing a thermodynamic variable of each of the setof regions. For example, as shown in FIGS. 1A through 1P, one or moreprocessors 106 of controller 102 may generate an initial fuel designparameter value 141 utilizing a thermodynamic variable (e.g.,temperature, pressure and the like) for each region 122. For instance,as shown in FIG. 1I, one or more processors 106 of controller 102 maygenerate an initial fuel design parameter value for a given region 122utilizing a thermodynamic variable for the given region 122. In anotherinstance, as shown in FIG. 1L, one or more processors 106 of controller102 may generate an initial fuel design parameter value for a givenregion 122 utilizing a thermodynamic variable for the region 122 andregions 123 a-123 f adjacent to the given region 122.

In another embodiment, the operation 1604 illustrates generating aninitial set of fuel design parameter values utilizing a neutronicparameter of each of the set of regions. For example, as shown in FIGS.1A through 1P, one or more processors 106 of controller 102 may generatean initial set of fuel design parameter values utilizing a neutronicparameter associated with the simulated nuclear fuel within of each ofthe set of regions. For instance, as shown in FIG. 1I, one or moreprocessors 106 of controller 102 may generate an initial fuel designparameter value for a given region 122 utilizing a neutronic parameterfor the given region 122. In another instance, as shown in FIG. 1L, oneor more processors 106 of controller 102 may generate an initial fueldesign parameter value for a given region 122 utilizing a neutronicparameter for region 122 and regions 123 a-123 f adjacent to the givenregion 122.

In another embodiment, the operation 1606 illustrates generating aninitial set of fuel design parameter values utilizing a k-infinity valueof each of the set of regions. For example, as shown in FIGS. 1A through1P, one or more processors 106 of controller 102 may generate an initialset of fuel design parameter values utilizing a k-infinity valueassociated with the nuclear fuel within each of the set of regions. Forinstance, as shown in FIG. 1I, one or more processors 106 of controller102 may generate an initial fuel design parameter value for a givenregion 122 utilizing a k-infinity value for the given region 122. Inanother instance, as shown in FIG. 1L, one or more processors 106 ofcontroller 102 may generate an initial fuel design parameter value for agiven region 122 utilizing a k-infinity value for region 122 and regions123 a-123 f adjacent to the given region 122.

FIG. 17 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 17 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 1702.

The operation 1702 illustrates generating an initial set of enrichmentvalues utilizing at least one design variable of each of the set ofregions. For example, as shown in FIGS. 1A through 1P, one or moreprocessors 106 of controller 102 may generate an initial set ofsimulated nuclear fuel enrichment value utilizing one or more designvariables (e.g., thermodynamic variable, neutronic parameter and thelike) for each region 122. For instance, as shown in FIG. 1I, one ormore processors 106 of controller 102 may generate an initial set ofenrichment values for a given region 122 utilizing a design variable forthe given region 122. In another instance, as shown in FIG. 1L, one ormore processors 106 of controller 102 may generate an initial set ofenrichment values for a given region 122 utilizing a design variable forregion 122 and regions 123 a-123 f adjacent to the given region 122.

FIG. 18 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 18 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 1802 and/or 1804.

The operation 1802 illustrates generating an initial set of pindimension values associated with a set of pins of a fuel assembly of thesimulated BOC core of the nuclear reactor utilizing at least one designvariable of each of the set of regions. For example, as shown in FIGS.1A through 1P, one or more processors 106 of controller 102 may generatean initial set of pin dimension values associated with a set of pins ofa fuel assembly 124 of the simulated BOC core 120 of the nuclear reactorutilizing one or more design variables of each of the set of regions122. For instance, as shown in FIG. 1I, one or more processors 106 ofcontroller 102 may generate an initial set of pin dimension valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing a design variable for thegiven region 122. In another instance, as shown in FIG. 1L, one or moreprocessors 106 of controller 102 may generate an initial set of pindimension values associated with a set of pins of a fuel assembly 124 ofthe simulated BOC core 120 of the nuclear reactor utilizing a designvariable for region 122 and each of the regions 123 a-122 f adjacent tothe given region 122.

In another embodiment, the operation 1804 illustrates generating aninitial set of pin configuration values associated with a set of pins ofa fuel assembly of the simulated BOC core of the nuclear reactorutilizing at least one design variable of each of the set of regions.For example, as shown in FIGS. 1A through 1P, one or more processors 106of controller 102 may generate an initial set of pin configurationvalues associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. For instance, one ormore processors 106 of controller 102 may generate an initial set of pinpitch values associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate an initialnumber of pins within a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122.

FIG. 19 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 19 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 1902.

In another embodiment, the operation 1902 illustrates generating aninitial set of pin geometry values associated with a set of pins of afuel assembly of the simulated BOC core of the nuclear reactor utilizingat least one design variable of each of the set of regions. For example,as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may generate an initial set of pin geometry valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. For instance, one or moreprocessors 106 of controller 102 may generate an initial set of pin sizevalues (e.g., pin length values, pin thickness/radius values and thelike) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate an initial setof pin shapes (e.g., hexagonoid, cylinder, prism and the like)associated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122.

FIG. 20 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 20 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 2002.

In another embodiment, the operation 2002 illustrates generating aninitial set of pin composition values associated with a set of pins of afuel assembly of the simulated BOC core of the nuclear reactor utilizingat least one design variable of each of the set of regions. For example,as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may generate an initial set of pin composition valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. For instance, one or moreprocessors 106 of controller 102 may generate a set of fuel smeardensities associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set offissile content values (i.e., relative amount of fissile material ineach pin) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set offertile content values (i.e., relative amount of fertile material ineach pin) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set ofnon-fissile/non-fertile content values (i.e., relative amount ofnon-fissile/non-fertile material in each pin (e.g., amount of zirconiumin each pin)) associated with a set of pins of a fuel assembly 124 ofthe simulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. By way of anotherexample, as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may generate an initial set of pin composition values asa function of position and/or fuel assembly location across thesimulated BOC core of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. In this regard, the one ormore processors 106 of controller 102 may control both the fuelcomposition of each pin of the fuel assemblies of the simulated BOC coreand the manner in which the fuel composition varies across the variousfuel assemblies of the simulated BOC core.

FIG. 21 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 21 illustrates example embodiments where thegenerating operation 440 may include at least one additional operation.Additional operations may include an operation 2102 and/or 2104.

The operation 2102 illustrates generating an initial set of fuel designparameter values utilizing at least one design variable of each of a setof pins of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the set of regions ofthe simulated BOC core of the nuclear reactor. For example, as shown inFIGS. 1A through 1P, one or more processors 106 of controller 102 maygenerate an initial set of fuel design parameter values associated withone of the set of regions of the simulated BOC core 120 utilizing atleast one design variable for each of the set of pins. Further, each ofthe initial set of fuel design parameter values may be associated withone of the set of regions of the simulated BOC core of the nuclearreactor. In this regard, the initial set of fuel design parameter valuesmay be generated at the “multi-pin” level (i.e., region includingmultiple pins) using pin-level inputs for the one or more designvariables.

The operation 2104 illustrates generating an initial set of fuel designparameter values utilizing at least one design variable of each of a setof pins of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the pins of each ofthe set of regions of the simulated BOC core of the nuclear reactor. Forexample, as shown in FIGS. 1A through 1P, one or more processors 106 ofcontroller 102 may generate an initial set of fuel design parametervalues associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 utilizing at least one design variable of each ofthe set of pins. Further, each of the initial set of fuel designparameter values may be associated with one of the pins of each of theset of regions of the simulated BOC core of the nuclear reactor. In thisregard, the initial set of fuel design parameter values may be generatedat the “pin-level” of the simulated reactor core using pin-level inputsfor the one or more design variables.

FIG. 22 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 22 illustrates example embodiments where thecalculating operation 450 may include at least one additional operation.Additional operations may include an operation 2202 and/or 2204.

The operation 2202 illustrates calculating a power density distributionof the simulated BOC core utilizing the generated initial set of fueldesign parameter values associated with the set of regions located atthe initial set of positions of the simulated BOC core. For example, asshown in FIGS. 1A through 1P, using the generated initial set of fueldesign parameter values corresponding to the regions 122 located at theinitial positions of the simulated BOC core 120, the one or moreprocessors 106 of controller 102 may calculate a power densitydistribution for the simulated BOC core 120.

In another embodiment, 2204 illustrates calculating a rate of change ofa power density distribution of the simulated BOC core utilizing thegenerated initial set of fuel design parameter values associated withthe set of regions located at the initial set of positions of thesimulated BOC core. For example, as shown in FIGS. 1A through 1P, usingthe generated initial set of fuel design parameter values correspondingto the regions 122 located at the initial positions of the simulated BOCcore 120, the one or more processors 106 of controller 102 may calculatea rate-of-change of power density distribution for the simulated BOCcore 120.

FIG. 23 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 23 illustrates example embodiments where thecalculating operation 450 may include at least one additional operation.Additional operations may include an operation 2302 and/or 2304.

The operation 2302 illustrates calculating a reactivity distribution ofthe simulated BOC core utilizing the generated initial set of fueldesign parameter values associated with the set of regions located atthe initial set of positions of the simulated BOC core. For example, asshown in FIGS. 1A through 1P, using the generated initial set of fueldesign parameter values corresponding to the regions 122 located at theinitial positions of the simulated BOC core 120, the one or moreprocessors 106 of controller 102 may calculate a reactivity distributionfor the simulated BOC core 120.

In another embodiment, operation 2304 illustrates calculating a rate ofchange of a power density distribution of the simulated BOC coreutilizing the generated initial set of fuel design parameter valuesassociated with the set of regions located at the initial set ofpositions of the simulated BOC core. For example, as shown in FIGS. 1Athrough 1P, using the generated initial set of fuel design parametervalues corresponding to the regions 122 located at the initial positionsof the simulated BOC core 120, the one or more processors 106 ofcontroller 102 may calculate a rate-of-change of reactivity distributionfor the simulated BOC core 120.

FIG. 24 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 24 illustrates example embodiments where thegenerating operation 460 may include at least one additional operation.Additional operations may include an operation 2402.

The operation 2402 illustrates generating a loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, thesubsequent set of positions defining the loading distribution for thesimulated BOC core. For example, as shown in FIGS. 1A through 1P, theone or more processors 106 of the controller 102 may generate a loadingdistribution by performing at least one perturbation process on the setof regions 122 of the simulated BOC core 120 in order to determine asubsequent set of positions for the set of regions within the simulatedBOC core, the subsequent set of positions defining the loadingdistribution for the simulated BOC core 120. For instance, thesubsequent positions of regions 122 outputted from the perturbationprocess 170 may serve to define a loading distribution (i.e., spatialdistribution of fertile and non-fertile components of nuclear fuel inreactor core) for the simulated BOC core 120.

FIG. 25 illustrates alternative embodiments of the example operationalflow 400 of FIG. 4A. FIG. 25 illustrates example embodiments where thegenerating operation 460 may include at least one additional operation.Additional operations may include an operation 2502.

The operation 2502 illustrates generating a loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, whereinthe subsequent set of positions reduce a deviation metric between the atleast one reactor core distribution of the simulated BOC core and thereceived at least one reactor core parameter distribution associatedwith a state of a core of a nuclear reactor below a selected tolerancelevel. For example, as shown in FIGS. 1A through 1P, the one or moreprocessors 106 of the controller 102 may generate a loading distributionby performing at least one perturbation process on the set of regions122 of the simulated BOC core 120 in order to determine a subsequent setof positions for the set of regions 122 within the simulated BOC core120. Further, the subsequent set of positions may serve to reduce adeviation metric between the at least one reactor core distribution ofthe simulated BOC core and the received at least one reactor coreparameter distribution associated with a state of a core of a nuclearreactor below a selected tolerance level. For instance, as shown in FIG.10, the perturbation procedure 170 may iteratively vary the positions ofthe regions 122 within the simulated core 120 until a deviation metric(e.g., difference, spatially averaged difference, maximum difference,minimum difference, aggregated global deviation metric and the like)between the one or more calculated reactor core distributions of thesimulated BOC core and the received one or more reactor core parameterdistributions associated with a state of a core of a reference nuclearreactor is reduced below a selected tolerance level.

FIG. 26 illustrates an operational flow 2600 representing exampleoperations related to generating a nuclear reactor core loadingdistribution. FIG. 26 illustrates an example embodiment where theexample operational flow 400 of FIG. 4A may include at least oneadditional operation. Additional operations may include an operation2602, 2604, 2606 and/or 2608.

The operation 2602 illustrates reporting the subsequent set of positionsof the set of regions of the simulated BOC core. For example, as shownin FIGS. 1A through 1P, the one or more processors 106 of controller 102may report the subsequent set of positions of the set of regions of thesimulated BOC core to a destination. For instance, the one or moreprocessors 106 of controller 102 may transmit one or more signalsindicative of the subsequent set of positions of the set of regions 122of the simulated BOC core 120 to a destination.

In another embodiment, operation 2604 illustrates reporting thesubsequent set of positions of the set of regions of the simulated BOCcore to a display. For example, as shown in FIGS. 1A through 1P, the oneor more processors 106 of controller 102 may report the subsequent setof positions of the set of regions of the simulated BOC core to adisplay (e.g., display associated with controller 102, display of remotesystem, display of nuclear reactor control system and the like). Forinstance, the one or more processors 106 of controller 102 may transmitone or more signals indicative of the subsequent set of positions of theset of regions 122 of the simulated BOC core 120 to a display.

In another embodiment, operation 2606 illustrates reporting thesubsequent set of positions of the set of regions of the simulated BOCcore to a memory. For example, as shown in FIGS. 1A through 1P, the oneor more processors 106 of controller 102 may report the subsequent setof positions of the set of regions of the simulated BOC core to a memory(e.g., memory of controller 102, memory of remote system, memory ofnuclear reactor control system and the like). For instance, the one ormore processors 106 of controller 102 may transmit one or more signalsindicative of the subsequent set of positions of the set of regions 122of the simulated BOC core 120 to a display.

In another embodiment, operation 2608 illustrates reporting thesubsequent set of positions of the set of regions of the simulated BOCcore to a control system of a nuclear reactor. For example, as shown inFIGS. 1A through 1P, the one or more processors 106 of controller 102may report the subsequent set of positions of the set of regions of thesimulated BOC core to a control system of a nuclear reactor (e.g.,reactor 101 of FIG. 2A). For instance, the one or more processors 106 ofcontroller 102 may transmit one or more signals indicative of thesubsequent set of positions of the set of regions 122 of the simulatedBOC core 120 to a control system of a nuclear reactor (e.g., reactor 101of FIG. 2A).

FIG. 27A illustrates an operational flow 2700 representing exampleoperations related to arranging one or more fuel assemblies of a nuclearreactor core according to a generated nuclear reactor core loadingdistribution. In FIG. 27A and in following figures that include variousexamples of operational flows, discussion and explanation may beprovided with respect to the above-described examples of FIGS. 1Athrough 2D, and/or with respect to other examples and contexts. However,it should be understood that the operational flows may be executed in anumber of other environments and contexts, and/or in modified versionsof FIGS. 1A through 2D. Also, although the various operational flows arepresented in the sequence(s) illustrated, it should be understood thatthe various operations may be performed in other orders than those whichare illustrated, or may be performed concurrently.

After a start operation, the operational flow 2700 moves to a receivingoperation 2710. The receiving operation 2710 depicts receiving at leastone reactor core parameter distribution 103 associated with a state(e.g., equilibrium state) of a core of a nuclear reactor (e.g.,reference nuclear reactor). For example, as shown in FIGS. 1A through2D, one or more processors 106 of the controller 102 are communicativelycoupled to a core parameter distribution source 104 and configured toreceive one or more reactor core parameter distributions 103 of a coreof a nuclear reactor in a given state (e.g., equilibrium state, a stateapproaching equilibrium, or a state of equilibrium onset) from the coreparameter distribution source 104 (e.g., memory). Further, the one ormore processors 106 of the controller 102 may receive a reactor coreparameter distribution for a core of the nuclear reactor in a givenstate in the form of a database or map (e.g., two-dimensional orthree-dimensional map) indicative of the reactor core parameter as afunction of position within the core of the nuclear reactor.

Then, generating operation 2720 depicts generating an initial fuelloading distribution for a simulated BOC core of the nuclear reactor.For example, FIGS. 1A through 2D, one or more processors 106 of thecontroller 102 may generate an initial fuel loading distribution for asimulated BOC core of the nuclear reactor.

Then, selecting operation 2730 depicts selecting an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor. For example, FIGS. 1A through 2D, the one ormore processors 106 of the controller 102 may select an initial set ofpositions associated with a set of regions within the simulated BOC coreof the nuclear reactor.

Then, generating operation 2740 depicts generating an initial set offuel design parameter values utilizing at least one design variable ofeach of the set of regions. For example, as shown in FIGS. 1A through2D, the one or more processors 106 of the controller 102 may generate aninitial set of fuel design parameter values utilizing at least onedesign variable of each of the set of regions.

Then, calculating operation 2750 depicts calculating at least onereactor core parameter distribution of the simulated BOC core utilizingthe generated initial set of fuel design parameter values associatedwith the set of regions located at the initial set of positions of thesimulated BOC core. For example, FIGS. 1A through 2D, the one or moreprocessors 106 of the controller 102 may calculate one or more reactorcore parameter distributions of the simulated BOC core utilizing thegenerated initial set of fuel design parameter values associated withthe set of regions located at the initial set of positions of thesimulated BOC core.

Then, loading distribution generating step 2760 depicts generating aloading distribution by performing at least one perturbation process onthe set of regions of the simulated BOC core in order to determine asubsequent set of positions for the set of regions within the simulatedBOC core. For example, the one or more processors 106 of the controller102 may generate a loading distribution by performing one or moreperturbation processes on the set of regions of the simulated BOC corein order to determine a subsequent set of positions for the set ofregions within the simulated BOC core.

Then, arranging operation 2770 depicts arranging at least one fuelassembly of a core of a nuclear reactor according to the subsequent setof positions of the set of regions of the simulated BOC core. Forexample, as shown in FIGS. 1A through 2D, the one or more processors 106of the controller 102 may direct the fuel handler 204 to arrange one ormore fuel assemblies of the core 202 of the nuclear reactor 101according to the subsequent set of positions of the set of regions ofthe simulated BOC core in the loading distribution generated by the oneor more processors 106. For instance, the one or more processors 106 maytransmit a signal representative of the subsequent set of positions ofthe set of regions 122 of the generated loading distribution to a fuelhandler controller 206. In turn, the controller 206 may direct the fuelhandler 204 to arrange (e.g., replace, re-position, and the like) one ormore fuel assemblies of the core 202 of the nuclear reactor 101according to the subsequent set of positions of the set of regions 122of the simulated BOC core 120 in the loading distribution generated bythe one or more processors 106.

FIG. 27B illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 27B illustrates example embodiments wherethe receiving operation 2710 may include at least one additionaloperation. Additional operations may include operation 2712.

The operation 2712 illustrates receiving at least one reactor coreparameter distribution associated with an equilibrium state of a core ofa nuclear reactor. For example, as shown in FIGS. 1A through 2D, one ormore processors 106 of controller 102 may receive one or more reactorcore parameter distributions 103 for a core of a nuclear reactor in anequilibrium state from a core parameter distribution source 104. By wayof another example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor in a stateapproaching equilibrium from a core parameter distribution source 104.By way of another example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor at an onsetof an equilibrium state from a core parameter distribution source 104.

FIG. 28 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 28 illustrates example embodiments where thereceiving operation 2710 may include at least one additional operation.Additional operations may include operations 2802 and/or 2804.

The operation 2802 illustrates receiving at least one reactor coreparameter distribution associated with a state of a core of a thermalnuclear reactor. For example, as shown in FIGS. 1A through 2D, one ormore processors 106 of controller 102 may receive one or more reactorcore parameter distributions 103 for a core of a thermal nuclear reactorfrom a core parameter distribution source 104. In this regard, the coreparameter distribution source 104 may store a reactor core parameterdistribution for a core of a reference thermal nuclear reactor. Then,the one or more processors 106 of controller 102 may retrieve thereactor core parameter distribution 103 for a core of the referencethermal nuclear reactor stored in the core parameter distribution source104.

In another embodiment, the operation 2804 illustrates receiving at leastone reactor core parameter distribution associated with a state of acore of a fast nuclear reactor. For example, as shown in FIGS. 1Athrough 2D, one or more processors 106 of controller 102 may receive oneor more reactor core parameter distributions 103 for a core of a fastnuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a reference fast nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactor core parameter distribution 103 for a core of thereference fast nuclear reactor stored in the core parameter distributionsource 104.

FIG. 29 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 29 illustrates example embodiments where thereceiving operation 2710 may include at least one additional operation.Additional operations may include an operation 2902, and/or operation2904.

In one embodiment, operation 2902 illustrates receiving at least onereactor core parameter distribution associated with a state of a core ofa breed-and-burn nuclear reactor. For example, as shown in FIGS. 1Athrough 2D, one or more processors 106 of controller 102 may receive oneor more reactor core parameter distributions 103 for a core of abreed-and-burn nuclear reactor from a core parameter distribution source104. In this regard, the core parameter distribution source 104 maystore a reactor core parameter distribution for a core of a referencebreed-and-burn nuclear reactor. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactor core parameter distribution 103for a core of the reference breed-and-burn nuclear reactor stored in thecore parameter distribution source 104.

In another embodiment, operation 2904 illustrates receiving at least onereactor core parameter distribution associated with a state of a core ofa traveling wave reactor. For example, as shown in FIGS. 1A through 2D,one or more processors 106 of controller 102 may receive one or morereactor core parameter distributions 103 for a core of a traveling wavenuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a reactorcore parameter distribution for a core of a reference traveling nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactor core parameter distribution 103 for a core of thereference traveling wave nuclear reactor stored in the core parameterdistribution source 104.

FIG. 30 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 30 illustrates example embodiments where thereceiving operation 2710 may include at least one additional operation.Additional operations may include an operation 3002, 3004 and/oroperation 3006.

The operation 3002 illustrates receiving a power density distributionassociated with a state of a core of a nuclear reactor. For example, asshown in FIGS. 1A through 2D, one or more processors 106 of controller102 may receive one or more power density distributions for a givenstate of a core of a nuclear reactor from a core parameter distributionsource 104. In this regard, the core parameter distribution source 104may store a power density distribution for a given state of a core of anuclear reactor. Then, the one or more processors 106 of controller 102may retrieve the power density distribution for a given state of a coreof a nuclear reactor stored in the core parameter distribution source104. Further, the one or more processors 106 of the controller 102 mayreceive a power density distribution for a core of the nuclear reactorin the form of a database or map (e.g., two-dimensional orthree-dimensional map) indicative of the power generation density as afunction of position within the core of the nuclear reactor.

In another embodiment, operation 3004 illustrates receiving a rate ofchange of a power density distribution associated with a state of a coreof a nuclear reactor. For example, as shown in FIGS. 1A through 2D, oneor more processors 106 of controller 102 may receive one or more powerdensity rate-of-change distributions for a given state of a core of anuclear reactor from a core parameter distribution source 104. In thisregard, the core parameter distribution source 104 may store a powerdensity rate-of-change distribution for a given state of core of anuclear reactor. Then, the one or more processors 106 of controller 102may retrieve the power density rate-of-change distribution for a givenstate of a core of a nuclear reactor stored in the core parameterdistribution source 104. Further, the one or more processors 106 of thecontroller 102 may receive a power density rate-of-change distributionfor a core of the nuclear reactor in the form of a database or map(e.g., two-dimensional or three-dimensional map) indicative of the rateof change of power generation density as a function of position withinthe core of the nuclear reactor.

In another embodiment, operation 3006 illustrates receiving a reactivitydistribution associated with a state of a core of a nuclear reactor. Forexample, as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may receive one or more reactivity distributions for agiven state of a core of a nuclear reactor from a core parameterdistribution source 104. In this regard, the core parameter distributionsource 104 may store a reactivity distribution for a given state of acore of a nuclear reactor. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactivity distribution for a givenstate of a core of a nuclear reactor stored in the core parameterdistribution source 104. Further, the one or more processors 106 of thecontroller 102 may receive a reactivity distribution for a core of thenuclear reactor in the form of a database or map (e.g., two-dimensionalor three-dimensional map) indicative of reactivity as a function ofposition within the core of the nuclear reactor.

FIG. 31 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 31 illustrates example embodiments where thereceiving operation 2710 may include at least one additional operation.Additional operations may include an operation 3102, and/or operation3104.

The operation 3102 illustrates receiving a rate of change of areactivity distribution associated with a state of a core of a nuclearreactor. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may receive one or more reactivityrate-of-change distributions for a given state of a core of a nuclearreactor from a core parameter distribution source 104. In this regard,the core parameter distribution source 104 may store a reactivityrate-of-change distribution for a given state of a core of a nuclearreactor. Then, the one or more processors 106 of controller 102 mayretrieve the reactivity rate-of-change distribution for a given state ofa core of a nuclear reactor stored in the core parameter distributionsource 104. Further, the one or more processors 106 of the controller102 may receive a reactivity rate-of-change distribution for a core ofthe nuclear reactor in the form of a database or map (e.g.,two-dimensional or three-dimensional map) indicative of the rate ofchange of reactivity as a function of position within the core of thenuclear reactor.

In another embodiment, the operation 3104 illustrates receiving at leastone reactor core parameter distribution associated with a state of acore of a nuclear reactor, the core including plutonium. For example, asshown in FIGS. 1A through 2D, one or more processors 106 of controller102 may receive one or more reactor core parameter distributions for agiven state of a nuclear reactor core including plutonium from a coreparameter distribution source 104. In this regard, the core parameterdistribution source 104 may store a reactor core parameter distributionfor a given state of a nuclear reactor core including plutonium. Then,the one or more processors 106 of controller 102 may retrieve thereactor core parameter distribution for a given state of a nuclearreactor core including plutonium stored in the core parameterdistribution source 104.

FIG. 32 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 32 illustrates example embodiments where thereceiving operation 2710 may include at least one additional operation.Additional operations may include an operation 3202 and/or operation3204.

The operation 3202 illustrates receiving at least one reactor coreparameter distribution associated with a state of a core of a nuclearreactor, the core including at least one fuel assembly. For example, asshown in FIGS. 1A through 2D, one or more processors 106 of controller102 may receive one or more reactor core parameter distributions 103 fora core of a nuclear reactor including one or more fuel assemblies from acore parameter distribution source 104. In this regard, the coreparameter distribution source 104 may store a reactor core parameterdistribution for a core of a nuclear reactor with one or more fuelassemblies. Then, the one or more processors 106 of controller 102 mayretrieve the reactor core parameter distribution 103 for a core of anuclear reactor with one or more fuel assemblies stored in the coreparameter distribution source 104.

Further, operation 3204 illustrates receiving at least one reactor coreparameter distribution associated with a state of a core of a nuclearreactor, the core including at least one fuel assembly including atleast one pin. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may receive one or more reactor coreparameter distributions 103 for a core of a nuclear reactor includingone or more fuel assemblies with one or more fuel pins from a coreparameter distribution source 104. In this regard, the core parameterdistribution source 104 may store a reactor core parameter distributionfor a core of a nuclear reactor with one or more fuel assemblies havingone or more fuel pins. Then, the one or more processors 106 ofcontroller 102 may retrieve the reactor core parameter distribution 103for a core of a nuclear reactor with one or more fuel assemblies havingone or more fuel pins stored in the core parameter distribution source104.

FIG. 33 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 33 illustrates example embodiments where thereference generating operation 2720 may include at least one additionaloperation. Additional operations may include an operation 3302 and/oroperation 3304.

The operation 3302 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor, at least aportion of the BOC core including recycled nuclear fuel. For example, asshown in FIGS. 1A through 2D, the one or more processors 106 of thecontroller 102 may generate an initial fuel loading distribution for asimulated BOC core of the nuclear reactor including recycled nuclearfuel. For instance, the one or more processors 106 of the controller 102may provide the spatial distribution of nuclear fuel (including fissileand non-fissile material) throughout a simulated BOC core (e.g.,throughout the fuel assemblies of a simulated BOC core) including atleast some recycled nuclear fuel (e.g., recycled uranium).

In another embodiment, operation 3304 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, at least a portion of the BOC core including unburned nuclearfuel. For example, as shown in FIGS. 1A through 2D, the one or moreprocessors 106 of the controller 102 may generate an initial fuelloading distribution for a simulated BOC core of the nuclear reactorincluding recycled nuclear fuel. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel throughout a simulated BOC core includingat least some unburned nuclear fuel (e.g., unburned uranium).

FIG. 34 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 34 illustrates example embodiments where thegenerating operation 2720 may include at least one additional operation.Additional operations may include an operation 3402 and/or operation3404.

The operation 3402 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor, at least aportion of the BOC core including enriched nuclear fuel. For example, asshown in FIGS. 1A through 2D, the one or more processors 106 of thecontroller 102 may generate an initial fuel loading distribution for asimulated BOC core of the nuclear reactor including enriched nuclearfuel. For instance, the one or more processors 106 of the controller 102may provide the spatial distribution of nuclear fuel throughout asimulated BOC core including at least some enriched nuclear fuel.

In another embodiment, operation 3404 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, at least a portion of the BOC core including enriched uraniumbased nuclear fuel. For example, as shown in FIGS. 1A through 2D, theone or more processors 106 of the controller 102 may generate an initialfuel loading distribution for a simulated BOC core of the nuclearreactor including enriched uranium. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel throughout a simulated BOC core includingat least some enriched uranium.

FIG. 35 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 35 illustrates example embodiments where thereference generating operation 2720 may include at least one additionaloperation. Additional operations may include an operation 3502 and/oroperation 3504.

The operation 3502 illustrates generating an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor via atleast one of user input and a controller. For example, as shown in FIGS.1A through 2D, the one or more processors 106 of the controller 102 maygenerate an initial fuel loading distribution for a simulated BOC coreof the nuclear reactor using user input and/or the controller 102. Forinstance, the one or more processors 106 of the controller 102 mayprovide the spatial distribution of nuclear fuel (including fissile andnon-fissile material) throughout a simulated BOC core utilizing apreprogrammed predictive algorithm executed by the one or moreprocessors 106 of the controller 102. In this regard, the predictivealgorithm may select the preferred initial fuel loading distributionbased on a variety parameters, such as, but not limited to, historicaldata correlating initial fuel loading distribution starting points andquality of final fuel loading distribution, user selected initial fuelloading distribution preferences and the like.

In another instance, the one or more processors 106 of the controller102 may provide the spatial distribution of nuclear fuel throughout asimulated BOC core utilizing user inputted data in conjunction with thecontroller 102. In this regard, the user may select an initial fuelloading distribution based on a number of options presented to the uservia user display 116. For example, the controller 102 may present theuser (e.g., present on display 116) with a plurality of initial fuelloading distributions based on an output of a preprogrammed predictivealgorithm. Based on this presentation of loading distributions ondisplay 116, the user may select the preferred initial loadingdistribution using a user input device 118.

In yet another instance, the one or more processors 106 of thecontroller 102 may provide the spatial distribution of nuclear fuelthroughout a simulated BOC core based primarily on user inputted data.In this regard, the user may select or input an initial fuel loadingdistribution into the controller 102. For example, a user may select theinitial fuel loading distribution by choosing the specific material ormaterials (fissile or non-fissile) for each fuel assembly or each pin ofeach fuel assembly across the simulated BOC core. Further, the user maymake this initial fuel selection utilizing a graphical user interface114 (e.g., display/mouse, touchscreen, display/keyboard and the like),allowing the user to select from a list of possible nuclear fuelmaterials (e.g., fissile or non-fissile materials) at each of thesimulated fuel assemblies or pins of each of the simulated fuelassemblies throughout the simulated BOC core. In this manner, the user,in a discretized manner, may build up the initial nuclear fuel loadingdistribution across the simulated BOC core (e.g., built up with fuelassembly-level resolution or built up with fuel pin-level resolution).The selected initial loading distribution may then be read into thememory 108 of the controller 102 and used by the one or more processors106 in subsequent steps of the present invention.

In another embodiment, operation 3504 illustrates generating an initialfuel loading distribution for a simulated beginning-of-life (BOL) coreof the nuclear reactor. For example, as shown in FIGS. 1A through 2D,the one or more processors 106 of the controller 102 may generate aninitial fuel loading distribution for a simulated beginning-of-life(BOL) core of the nuclear reactor. For instance, the one or moreprocessors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel throughout a simulated BOL core (e.g.,throughout the fuel assemblies of a simulated BOL core) of the nuclearreactor.

FIG. 36 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 36 illustrates example embodiments where thegenerating operation 2720 may include at least one additional operation.Additional operations may include an operation 3602 and/or operation3604.

The operation 3602 illustrates randomly generating an initial fuelloading distribution for a simulated BOC core of the nuclear reactor.For example, as shown in FIGS. 1A through 2D, the one or more processors106 of the controller 102 may randomly generate an initial fuel loadingdistribution for a simulated BOC core of the nuclear reactor. Forinstance, the one or more processors 106 of the controller 102 may applya preprogrammed algorithm configured to randomly select the spatialdistribution of nuclear fuel (e.g., spatial distribution of fissile andnon-fissile material) across the simulated BOC core.

In another embodiment, operation 3604 illustrates generating an initialfuel loading distribution for a simulated BOC core of the nuclearreactor, the simulated BOC core of the nuclear reactor including aplurality of simulated fuel assemblies. For example, as shown in FIGS.1A through 2D, the one or more processors 106 of the controller 102 maygenerate an initial fuel loading distribution through a plurality ofsimulated fuel assemblies for a simulated BOC core of the nuclearreactor. For instance, the one or more processors 106 of the controller102 may provide the spatial distribution of nuclear fuel (e.g., spatialdistribution of fissile and non-fissile material) throughout simulatedBOC core by providing the type and quantity of material within each ofthe fuel assemblies throughout the simulated BOC core 120. Further, theinitial fuel loading distribution may be resolved at the pin-level ofeach fuel assembly of the simulated BOC core. In this regard, the one ormore processors 106 of the controller 102 may provide the spatialdistribution of nuclear fuel throughout the simulated BOC core byproviding the type and quantity of material within each fuel pin of eachfuel assembly throughout the simulated BOC core 120.

FIG. 37 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 37 illustrates example embodiments where theselecting operation 2730 may include at least one additional operation.Additional operations may include an operation 3702 and/or operation3704.

The operation 3702 illustrates selecting an initial set of positionsassociated with a set of regions within the simulated BOC core of thenuclear reactor, each of the initial set of positions corresponding toone of the set of regions. For example, as shown in FIGS. 1A through 2D,one or more processors 106 of controller 102 may select an initial setof positions (e.g., x, y, z positions) associated with a set of regions122 within the simulated BOC core of the nuclear reactor. Further, theone or more processors 106 of the controller 102 may assign a relativeposition to each of a set of regions within the simulated BOC core 120of the nuclear reactor. In this regard, each region as delineated by thecontroller 102 may encompass a selected volume (e.g., selected bycontroller or selected via user input) of the nuclear fuel within thesimulated BOC core 120.

In another embodiment, the operation 3704 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set regions, each regionencompassing at least one fuel assembly. For example, as shown in FIGS.1A through 2D, one or more processors 106 of controller 102 may selectan initial set of positions (e.g., x, y, z positions) associated with aset of regions 122 within the simulated BOC core 120 of the nuclearreactor, whereby each region encompasses one or more fuel assemblies 124of the simulated BOC core 120. Further, the one or more processors 106of the controller 102 may assign a relative position to each regionencompassing one or more fuel assemblies 124 within the simulated BOCcore 120 of the nuclear reactor. For instance, as shown in FIG. 1I, theone or more processors 106 of the controller 102 are configured toselect an initial set of positions 140 of the set of regions 122,whereby each region 122 encompasses a single fuel assembly 124 of theBOC core 120. In another instance, as shown in FIG. 1J, the one or moreprocessors 106 of the controller 102 are configured to select an initialset of positions 140 of the set of regions 122, whereby each region 122encompasses multiple fuel assemblies 124 of the BOC core 120.

FIG. 38 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 38 illustrates example embodiments where theselecting operation 2730 may include at least one additional operation.Additional operations may include an operation 3802.

In one embodiment, the operation 3802 illustrates selecting an initialset of positions associated with a set of regions within the simulatedBOC core of the nuclear reactor, each of the initial set of positionscorresponding to one of the set of regions, each of the set of regionsbeing a three dimensional region having a selected volume. For example,as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may select an initial set of positions 140 associatedwith a set of regions 122 within the simulated BOC core 120 of thenuclear reactor, whereby each region is a three dimensional regionhaving a selected volume. Further, the one or more processors 106 of thecontroller 102 may assign a relative position to each three dimensionalregion of selected volume within the simulated BOC core 120 of thenuclear reactor.

FIG. 39 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 39 illustrates example embodiments where theselecting operation 2730 may include at least one additional operation.Additional operations may include an operation 3902.

In one embodiment, the operation 3902 illustrates selecting an initialset of positions associated with a set of regions within the simulatedBOC core of the nuclear reactor, each of the initial set of positionscorresponding to one of the set of regions, each of the set of regionsbeing a three dimensional region having a selected shape. For example,as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may select an initial set of positions 140 associatedwith a set of regions 122 within the simulated BOC core 120 of thenuclear reactor, whereby each region is a three dimensional regionhaving a selected shape (e.g., hexagonoid, cuboid, cylinder, ellipsoid,sphere, disc, ring and the like). Further, the one or more processors106 of the controller 102 may assign a relative position to each threedimensional region of selected shape within the simulated BOC core 120of the nuclear reactor.

FIG. 40 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 40 illustrates example embodiments where theselecting operation 2730 may include at least one additional operation.Additional operations may include an operation 4002.

In another embodiment, the operation 4002 illustrates selecting aninitial set of positions associated with a set of regions within thesimulated BOC core of the nuclear reactor, each of the initial set ofpositions corresponding to one of the set of regions, the set of regionsincluding a selected number of regions. For example, as shown in FIGS.1A through 2D, one or more processors 106 of controller 102 may selectan initial set of positions 140 associated with a set of regions 122including a selected number of regions. Further, the one or moreprocessors 106 of the controller 102 may assign a relative position toeach region of the selected number of regions within the simulated BOCcore 120 of the nuclear reactor.

FIG. 41 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 41 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4102.

The operation 4102 illustrates generating an initial set of fuel designparameter values utilizing a thermodynamic variable of each of the setof regions. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may generate an initial fuel designparameter value 141 utilizing a thermodynamic variable (e.g.,temperature, pressure and the like) for each region 122. For instance,as shown in FIG. 1I, one or more processors 106 of controller 102 maygenerate an initial fuel design parameter value for a given region 122utilizing a thermodynamic variable 145 for the given region 122. Inanother instance, as shown in FIG. 1L, one or more processors 106 ofcontroller 102 may generate an initial fuel design parameter value for agiven region 122 utilizing a thermodynamic variable for the region 122and regions 123 a-123 f adjacent to the given region 122.

FIG. 42 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 42 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4202 and/or 4204.

The operation 4202 illustrates generating an initial set of fuel designparameter values utilizing a neutronic parameter of each of the set ofregions. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may generate an initial set of fueldesign parameter values utilizing a neutronic parameter associated withthe simulated nuclear fuel within of each of the set of regions. Forinstance, as shown in FIG. 1I, one or more processors 106 of controller102 may generate an initial fuel design parameter value for a givenregion 122 utilizing a neutronic parameter for the given region 122. Inanother instance, as shown in FIG. 1L, one or more processors 106 ofcontroller 102 may generate an initial fuel design parameter value for agiven region 122 utilizing a neutronic parameter for region 122 andregions 123 a-123 f adjacent to the given region 122.

In another embodiment, the operation 4204 illustrates generating aninitial set of fuel design parameter values utilizing a k-infinity valueof each of the set of regions. For example, as shown in FIGS. 1A through2D, one or more processors 106 of controller 102 may generate an initialset of fuel design parameter values utilizing a k-infinity valueassociated with the nuclear fuel within each of the set of regions. Forinstance, as shown in FIG. 1I, one or more processors 106 of controller102 may generate an initial fuel design parameter value for a givenregion 122 utilizing a k-infinity value for the given region 122. Inanother instance, as shown in FIG. 1L, one or more processors 106 ofcontroller 102 may generate an initial fuel design parameter value for agiven region 122 utilizing a k-infinity value for region 122 and regions123 a-123 f adjacent to the given region 122.

FIG. 43 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 43 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4302.

The operation 4302 illustrates generating an initial set of enrichmentvalues utilizing at least one design variable of each of the set ofregions. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of controller 102 may generate an initial set ofsimulated nuclear fuel enrichment value utilizing one or more designvariables (e.g., thermodynamic variable, neutronic parameter and thelike) for each region 122. For instance, as shown in FIG. 1I, one ormore processors 106 of controller 102 may generate an initial set ofenrichment values for a given region 122 utilizing a design variable forthe given region 122. In another instance, as shown in FIG. 1L, one ormore processors 106 of controller 102 may generate an initial set ofenrichment values for a given region 122 utilizing a design variable forregion 122 and regions 123 a-123 f adjacent to the given region 122.

FIG. 44 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 44 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4402 and/or operation4404.

The operation 4402 illustrates generating an initial set of pindimension values associated with a set of pins of a fuel assembly of thesimulated BOC core of the nuclear reactor utilizing at least one designvariable of each of the set of regions. For example, as shown in FIGS.1A through 2D, one or more processors 106 of controller 102 may generatean initial set of pin dimension values associated with a set of pins ofa fuel assembly 124 of the simulated BOC core 120 of the nuclear reactorutilizing one or more design variables of each of the set of regions122. For instance, as shown in FIG. 1I, one or more processors 106 ofcontroller 102 may generate an initial set of pin dimension valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing a design variable for thegiven region 122. In another instance, as shown in FIG. 1L, one or moreprocessors 106 of controller 102 may generate an initial set of pindimension values associated with a set of pins of a fuel assembly 124 ofthe simulated BOC core 120 of the nuclear reactor utilizing a designvariable for region 122 and regions 123 a-123 f adjacent to the givenregion 122.

In another embodiment, the operation 4404 illustrates generating aninitial set of pin configuration values associated with a set of pins ofa fuel assembly of the simulated BOC core of the nuclear reactorutilizing at least one design variable of each of the set of regions.For example, as shown in FIGS. 1A through 2D, one or more processors 106of controller 102 may generate an initial set of pin configurationvalues associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. For instance, one ormore processors 106 of controller 102 may generate an initial set of pinpitch values associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate an initialnumber of pins within a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122.

FIG. 45 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 45 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4502.

In another embodiment, the operation 4502 illustrates generating aninitial set of pin geometry values associated with a set of pins of afuel assembly of the simulated BOC core of the nuclear reactor utilizingat least one design variable of each of the set of regions. For example,as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may generate an initial set of pin geometry valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. For instance, one or moreprocessors 106 of controller 102 may generate an initial set of pin sizevalues (e.g., pin length values, pin thickness/radius values and thelike) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate an initial setof pin shapes (e.g., hexagonoid, cylinder, prism and the like)associated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122.

FIG. 46 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 46 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4602.

In another embodiment, the operation 4602 illustrates generating aninitial set of pin composition values associated with a set of pins of afuel assembly of the simulated BOC core of the nuclear reactor utilizingat least one design variable of each of the set of regions. For example,as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may generate an initial set of pin composition valuesassociated with a set of pins of a fuel assembly 124 of the simulatedBOC core 120 of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. For instance, one or moreprocessors 106 of controller 102 may generate a set of fuel smeardensities associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set offissile content values (i.e., relative amount of fissile material ineach pin) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set offertile content values (i.e., relative amount of fertile material ineach pin) associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. In another instance,one or more processors 106 of controller 102 may generate a set ofnon-fissile/non-fertile content values (i.e., relative amount ofnon-fissile/non-fertile material in each pin (e.g., amount of zirconiumin each pin)) associated with a set of pins of a fuel assembly 124 ofthe simulated BOC core 120 of the nuclear reactor utilizing one or moredesign variables of each of the set of regions 122. By way of anotherexample, as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may generate an initial set of pin composition values asa function of position and/or fuel assembly location across thesimulated BOC core of the nuclear reactor utilizing one or more designvariables of each of the set of regions 122. In this regard, the one ormore processors 106 of controller 102 may control both the fuelcomposition of each pin of the fuel assemblies of the simulated BOC coreand the manner in which the fuel composition varies across the variousfuel assemblies of the simulated BOC core.

FIG. 47 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 47 illustrates example embodiments where thegenerating operation 2740 may include at least one additional operation.Additional operations may include an operation 4702 and/or 4704.

The operation 4702 illustrates generating an initial set of fuel designparameter values utilizing at least one design variable of each of a setof pins of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the set of regions ofthe simulated BOC core of the nuclear reactor. For example, as shown inFIGS. 1A through 2D, one or more processors 106 of controller 102 maygenerate an initial set of fuel design parameter values associated withone of the set of regions of the simulated BOC core 120 utilizing atleast one design variable for each of the set of pins. Further, each ofthe initial set of fuel design parameter values may be associated withone of the set of regions of the simulated BOC core of the nuclearreactor. In this regard, the initial set of fuel design parameter valuesmay be generated at the “multi-pin” level (i.e., region includingmultiple pins) using pin-level inputs for the one or more designvariables.

The operation 4704 illustrates generating an initial set of fuel designparameter values utilizing at least one design variable of each of a setof pins of the set of regions, wherein each of the initial set of fueldesign parameter values is associated with one of the pins of each ofthe set of regions of the simulated BOC core of the nuclear reactor. Forexample, as shown in FIGS. 1A through 2D, one or more processors 106 ofcontroller 102 may generate an initial set of fuel design parametervalues associated with a set of pins of a fuel assembly 124 of thesimulated BOC core 120 utilizing at least one design variable of each ofthe set of pins. Further, each of the initial set of fuel designparameter values may be associated with one of the pins of each of theset of regions of the simulated BOC core of the nuclear reactor. In thisregard, the initial set of fuel design parameter values may be generatedat the “pin-level” (i.e., each region includes a single pin) of thesimulated reactor core using pin-level inputs for the one or more designvariables.

FIG. 48 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 48 illustrates example embodiments where thecalculating operation 2750 may include at least one additionaloperation. Additional operations may include an operation 4802 and/or4804.

The operation 4802 illustrates calculating a power density distributionof the simulated BOC core utilizing the generated initial set of fueldesign parameter values associated with the set of regions located atthe initial set of positions of the simulated BOC core. For example, asshown in FIGS. 1A through 2D, using the generated initial set of fueldesign parameter values corresponding to the regions 122 located at theinitial positions of the simulated BOC core 120, the one or moreprocessors 106 of controller 102 may calculate a power densitydistribution for the simulated BOC core 120.

In another embodiment, 4804 illustrates calculating a rate of change ofa power density distribution of the simulated BOC core utilizing thegenerated initial set of fuel design parameter values associated withthe set of regions located at the initial set of positions of thesimulated BOC core. For example, as shown in FIGS. 1A through 2D, usingthe generated initial set of fuel design parameter values correspondingto the regions 122 located at the initial positions of the simulated BOCcore 120, the one or more processors 106 of controller 102 may calculatea rate-of-change of power density distribution for the simulated BOCcore 120.

FIG. 49 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 49 illustrates example embodiments where thecalculating operation 2750 may include at least one additionaloperation. Additional operations may include an operation 4902 and/or4904.

The operation 4902 illustrates calculating a reactivity distribution ofthe simulated BOC core utilizing the generated initial set of fueldesign parameter values associated with the set of regions located atthe initial set of positions of the simulated BOC core. For example, asshown in FIGS. 1A through 2D, using the generated initial set of fueldesign parameter values corresponding to the regions 122 located at theinitial positions of the simulated BOC core 120, the one or moreprocessors 106 of controller 102 may calculate a reactivity distributionfor the simulated BOC core 120.

In another embodiment, operation 4904 illustrates calculating a rate ofchange of a power density distribution of the simulated BOC coreutilizing the generated initial set of fuel design parameter valuesassociated with the set of regions located at the initial set ofpositions of the simulated BOC core. For example, as shown in FIGS. 1Athrough 2D, using the generated initial set of fuel design parametervalues corresponding to the regions 122 located at the initial positionsof the simulated BOC core 120, the one or more processors 106 ofcontroller 102 may calculate a rate-of-change of reactivity distributionfor the simulated BOC core 120.

FIG. 50 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 50 illustrates example embodiments where thegenerating operation 2760 may include at least one additional operation.Additional operations may include an operation 5002.

The operation 5002 illustrates generating a loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, thesubsequent set of positions defining the loading distribution for thesimulated BOC core. For example, as shown in FIGS. 1A through 2D, theone or more processors 106 of the controller 102 may generate a loadingdistribution by performing at least one perturbation process on the setof regions 122 of the simulated BOC core 120 in order to determine asubsequent set of positions for the set of regions within the simulatedBOC core, the subsequent set of positions defining the loadingdistribution for the simulated BOC core 120. For instance, thesubsequent positions of regions 122 outputted from the perturbationprocess 170 may serve to define a loading distribution (i.e., spatialdistribution of fertile and non-fertile components of nuclear fuel inreactor core) for the simulated BOC core 120.

FIG. 51 illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 51 illustrates example embodiments where thegenerating operation 2760 may include at least one additional operation.Additional operations may include an operation 5102.

The operation 2502 illustrates generating a loading distribution byperforming at least one perturbation process on the set of regions ofthe simulated BOC core in order to determine a subsequent set ofpositions for the set of regions within the simulated BOC core, whereinthe subsequent set of positions reduce a deviation metric between the atleast one reactor core distribution of the simulated BOC core and thereceived at least one reactor core parameter distribution associatedwith a state of a core of a nuclear reactor below a selected tolerancelevel. For example, as shown in FIGS. 1A through 2D, the one or moreprocessors 106 of the controller 102 may generate a loading distributionby performing at least one perturbation process on the set of regions122 of the simulated BOC core 120 in order to determine a subsequent setof positions for the set of regions 122 within the simulated BOC core120. Further, the subsequent set of positions may serve to reduce adeviation metric between the at least one reactor core distribution ofthe simulated BOC core and the received at least one reactor coreparameter distribution associated with a state of a core of a nuclearreactor below a selected tolerance level. For instance, as shown in FIG.1P, the perturbation procedure 170 may iteratively vary the positions ofthe regions 122 within the simulated core 120 until a deviation metric(e.g., difference, spatially averaged difference, maximum difference,minimum difference, aggregated global deviation metric and the like)between the one or more calculated reactor core distributions of thesimulated BOC core and the received one or more reactor core parameterdistributions associated with a state of a core of a reference nuclearreactor is reduced below a selected tolerance level.

FIG. 52A illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 52A illustrates example embodiments wherethe arranging operation 2770 may include at least one additionaloperation. Additional operations may include an operation 5202 and/or5204.

The operation 5202 illustrates, responsive to the loading distributiondetermination, arranging at least one fuel assembly of the core of thenuclear reactor according to the subsequent set of simulated positionsof the set of regions of the simulated BOC nuclear reactor core. Forexample, as shown in FIGS. 1A through 2D, upon determining the loadingdistribution of the simulated BOC core 120, one or more processors 106of the controller 102 may direct the fuel handler 204 to arrange one ormore fuel assemblies 208 of the reactor core 202 of reactor 101 inaccordance with the subsequent set of simulated positions of the set ofregions 122 of the simulated BOC nuclear reactor core 120. For instance,one or more processors 106 of the controller 102 may transmit a commandsignal 207 indicative of the set of subsequent set of positions of theset of regions of the simulated BOC nuclear reactor core 120 to the fuelhandler controller 206. In turn, the fuel handler controller 206 maytransmit a command signal 209 encoded with instructions necessary forthe fuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of reactor 101 in accordance with the subsequent set ofpositions of the set of regions 122 of the simulated BOC nuclear reactorcore 120.

In another embodiment, the operation 5204 illustrates, responsive to auser input, arranging at least one fuel assembly of the core of thenuclear reactor according to the subsequent set of simulated positionsof the set of regions 122 of the simulated BOC nuclear reactor core 120.For example, as shown in FIGS. 1A through 2D, in response to a signalfrom a user input device 118, one or more processors 106 of thecontroller 102 may direct the fuel handler 204 to arrange one or morefuel assemblies 208 of the reactor core 202 of reactor 101 in accordancewith the subsequent set of simulated positions of the set of regions 122of the simulated BOC nuclear reactor core 120. For instance, uponreceiving a command signal from a user input device 118 indicative of auser selection, one or more processors 106 of the controller 102 maytransmit a command signal 207 indicative of the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120 to the fuel handler controller 206. In turn,the fuel handler controller 206 may transmit a command signal 209encoded with instructions necessary for the fuel handler 204 to arrangeone or more fuel assemblies 208 of the reactor core 202 of reactor 101in accordance with the subsequent set of simulated positions of the setof regions 122 of the simulated BOC nuclear reactor core 120.

FIG. 52B illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 52B illustrates example embodiments wherethe arranging operation 2770 may include at least one additionaloperation. Additional operations may include an operation 5206 and/or5208.

The operation 5206 illustrates arranging at least one fuel assembly of acore of a thermal nuclear reactor according to the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 toarrange one or more fuel assemblies 208 of the reactor core 202 of athermal nuclear reactor in accordance with the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120. For instance, one or more processors 106 ofthe controller 102 may transmit a command signal 207 indicative of thesubsequent set of simulated positions of the set of regions 122 of thesimulated BOC nuclear reactor core 120 to the fuel handler controller206. In turn, the fuel handler controller 206 may transmit a commandsignal 209 encoded with instructions necessary for the fuel handler 204to arrange one or more fuel assemblies 208 of the reactor core 202 of athermal nuclear reactor in accordance with the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120.

The operation 5208 illustrates arranging at least one fuel assembly of acore of a fast nuclear reactor according to the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 toarrange one or more fuel assemblies 208 of the reactor core 202 of afast nuclear reactor in accordance with the subsequent set of simulatedpositions of the set of regions 122 of the simulated BOC nuclear reactorcore 120. For instance, one or more processors 106 of the controller 102may transmit a command signal 207 indicative of the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120 to the fuel handler controller 206. In turn,the fuel handler controller 206 may transmit a command signal 209encoded with instructions necessary for the fuel handler 204 to arrangeone or more fuel assemblies 208 of the reactor core 202 of a fastnuclear reactor in accordance with the subsequent set of simulatedpositions of the set of regions 122 of the simulated BOC nuclear reactorcore 120.

FIG. 52C illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 52C illustrates example embodiments wherethe arranging operation 2770 may include at least one additionaloperation. Additional operations may include an operation 5210 and/or5212.

The operation 5210 illustrates arranging at least one fuel assembly of acore of a breed-and-burn nuclear reactor according to the set ofsimulated positions of the set of regions of the simulated BOC nuclearreactor core. For example, as shown in FIGS. 1A through 2D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 toarrange one or more fuel assemblies 208 of the reactor core 202 of abreed-and-burn nuclear reactor in accordance with the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120. For instance, one or more processors 106 ofthe controller 102 may transmit a command signal 207 indicative of thesubsequent set of simulated positions of the set of regions 122 of thesimulated BOC nuclear reactor core 120 to the fuel handler controller206. In turn, the fuel handler controller 206 may transmit a commandsignal 209 encoded with instructions necessary for the fuel handler 204to arrange one or more fuel assemblies 208 of the reactor core 202 of abreed-and-burn nuclear reactor in accordance with the subsequent set ofsimulated positions of the set of regions 122 of the simulated BOCnuclear reactor core 120.

In another embodiment, the operation 5212 illustrates arranging at leastone fuel assembly of a core of a traveling wave nuclear reactoraccording to the set of simulated positions of the set of regions of thesimulated BOC nuclear reactor core. For example, as shown in FIGS. 1Athrough 2D, one or more processors 106 of the controller 102 may directthe fuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of a traveling wave nuclear reactor in accordance withthe subsequent set of simulated positions of the set of regions 122 ofthe simulated BOC nuclear reactor core 120. For instance, one or moreprocessors 106 of the controller 102 may transmit a command signal 207indicative of the subsequent set of simulated positions of the set ofregions 122 of the simulated BOC nuclear reactor core 120 to the fuelhandler controller 206. In turn, the fuel handler controller 206 maytransmit a command signal 209 encoded with instructions necessary forthe fuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of a traveling wave nuclear reactor in accordance withthe subsequent set of simulated positions of the set of regions 122 ofthe simulated BOC nuclear reactor core 120.

FIG. 52D illustrates alternative embodiments of the example operationalflow 2700 of FIG. 27A. FIG. 52D illustrates example embodiments wherethe arranging operation 2770 may include at least one additionaloperation. Additional operations may include an operation 5214 and/or5216.

The operation 5214 illustrates translating at least one fuel assembly ofthe core of the nuclear reactor from an initial location to a subsequentlocation according to the subsequent set of positions of the set ofregions of the simulated BOC core. For example, as shown in FIGS. 1Athrough 2D, one or more processors 106 of the controller 102 may directthe fuel handler 204 to translate one or more fuel assemblies 208 of thecore 202 of the nuclear reactor 101 from an initial location to asubsequent location according to the subsequent set of positions of theset of regions 122 of the simulated BOC nuclear reactor core 120. Forinstance, one or more processors 106 of the controller 102 may directthe gripper 214 of fuel handler 204 to withdraw a selected fuel assembly212 and move the selected fuel assembly to a new location within thenuclear reactor core 202 according to the subsequent set of simulatedpositions of the set of regions 122 of the simulated BOC nuclear reactorcore 120.

In another embodiment, the operation 5216 illustrates replacing at leastone fuel assembly of the core of the nuclear reactor according to thesubsequent set of simulated positions of the set of regions of thesimulated BOC core. For example, as shown in FIGS. 1A through 2D, one ormore processors 106 of the controller 102 may direct the fuel handler204 to replace one or more fuel assemblies 208 of the core 202 of thenuclear reactor 101 according to the subsequent set of positions of theset of regions 122 of the simulated BOC nuclear reactor core. 120. Forinstance, one or more processors 106 of the controller 102 may directthe gripper 214 of fuel handler 204 to withdraw a selected fuel assembly212 and move the selected fuel assembly to a storage location outside ofthe reactor core 202. In turn, the one or more processors 106 may directthe gripper 214 (or an additional gripper) to insert a new fuel assemblyinto the reactor core 202 at the location of the removed fuel assembly212. It is noted herein that by repeating this process the system 200may form (or re-assemble) the reactor core 202 in accordance with theset of simulated positions of the set of regions of the simulated BOCnuclear reactor core.

FIG. 53 illustrates an operational flow 5300 representing exampleoperations related to arranging one or more fuel assemblies of a nuclearreactor core according to a generated nuclear reactor core loadingdistribution. FIG. 53 illustrates an example embodiment where theexample operational flow 5300 of FIG. 53 may include at least oneadditional operation. Additional operations may include reportingoperations 5302, 5304 and/or 5306.

The operation 5302 illustrates reporting the subsequent set of positionsof the set of regions of the simulated BOC core. For example, as shownin FIGS. 1A through 2D, the one or more processors 106 of controller 102may report the subsequent set of positions of the set of regions of thesimulated BOC core to a destination. For instance, the one or moreprocessors 106 of controller 102 may transmit one or more signalsindicative of the subsequent set of positions of the set of regions ofthe simulated BOC core to a destination.

In another embodiment, the operation 5304 illustrates reporting thesubsequent set of positions of the set of regions of the simulated BOCcore to a display. For example, as shown in FIGS. 1A through 2D, the oneor more processors 106 of controller 102 may report the subsequent setof positions of the set of regions of the simulated BOC core 120 to adisplay (e.g., audio or visual display). For instance, the one or moreprocessors 106 of controller 102 may transmit one or more signalsindicative of the subsequent set of positions of the set of regions ofthe simulated BOC core 120 to a display unit 116.

In another embodiment, the operation 5306 illustrates reporting thesubsequent set of positions of the set of regions of the simulated BOCcore to a memory. For example, as shown in FIGS. 1A through 2D, the oneor more processors 106 of controller 102 may report the subsequent setof positions of the set of regions of the simulated BOC core to a memorydevice. For instance, the one or more processors 106 of controller 102may transmit one or more signals indicative of the subsequent set ofpositions of the set of regions of the simulated BOC core 120 to amemory device 108.

FIG. 54 illustrates alternative embodiments of the example operationalflow 5300 of FIG. 53. FIG. 54 illustrates example embodiments where thereporting operation 5302 may include at least one additional operation.Additional operations may include an operation 5402.

The operation 5402 illustrates reporting the subsequent set of positionsof the set of regions of the simulated BOC core to a control system ofthe nuclear reactor. For example, as shown in FIGS. 1A through 2D, theone or more processors 106 of controller 102 may report the subsequentset of positions of the set of regions of the simulated BOC core 120 toa control system 180 of the nuclear reactor 101. For instance, the oneor more processors 106 of controller 102 may transmit one or moresignals indicative of the subsequent set of positions of the set ofregions of the simulated BOC core 120 to a control system 180 of thenuclear reactor 101.

FIG. 55 illustrates an operational flow 5500 representing exampleoperations related to determining an operation compliance state of acore of a nuclear reactor. In FIG. 55 and in following figures thatinclude various examples of operational flows, discussion andexplanation may be provided with respect to the above-described examplesof FIGS. 1A through 3D, and/or with respect to other examples andcontexts. However, it should be understood that the operational flowsmay be executed in a number of other environments and contexts, and/orin modified versions of FIGS. 1A through 3D. Also, although the variousoperational flows are presented in the sequence(s) illustrated, itshould be understood that the various operations may be performed inother orders than those which are illustrated, or may be performedconcurrently.

After a start operation, the operational flow 5500 moves to an initialloading distribution determining operation 5510. The determiningoperation 5510 depicts determining an initial loading distribution of acore of a nuclear reactor utilizing a BOC simulation process to generatea simulated BOC nuclear reactor core. For example, as shown in FIGS. 1Athrough 3D, one or more processors 106 of the controller 102 areconfigured to determine an initial loading distribution of a core of anuclear reactor utilizing a BOC simulation process to generate asimulated BOC nuclear reactor core 120. For instance, the one or moreprocessors 106 of controller 102 may implement a process, such as, butnot limited to process 400 of the present disclosure in order togenerate a simulated BOC nuclear reactor core.

Then, arranging step operation 5520 depicts arranging at least one fuelassembly of the core of the nuclear reactor according to a set ofsimulated positions of a set of regions of the simulated BOC nuclearreactor core. For example, as shown in FIGS. 1A through 3D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 ofsystem 300 to arrange (e.g., translate or replace) one or more fuelassemblies 208 of reactor core 202 according to a set of simulatedpositions of a set of regions of the simulated BOC nuclear reactor core120.

Then, core operating operation 5530 depicts operating the core of thenuclear reactor for a selected time interval. For example, as shownFIGS. 1A through 3D, the nuclear reactor system 300 may operate the core202 of nuclear reactor 101. Following operation of the reactor core 202for a selected time interval, the one or more processors 106 of thecontroller 102 may execute a core measuring step.

Then, measured core parameter distribution generating operation 5540depicts generating a measured reactor core parameter distributionutilizing at least one measurement of at least one reactor coreparameter at one or more locations within the core of the nuclearreactor. For example, as shown in FIGS. 1A through 3D, the system 300may include a reactor core measurement system 302 configured to measureone or more reactor core parameters at one or more locations of thenuclear reactor core 202. Then, based on the measurements from thereactor core measurement system 302, the one or more processors 106 ofthe controller 102 may generate a measured reactor core parameterdistribution. For instance, based on the measurements from the reactorcore measurement system 302, the one or more processors 106 ofcontroller 102 may generate at least one of a measured power densitydistribution, a measured power density rate-of-change distribution, ameasured reactivity distribution, a measured reactivity rate-of-changedistribution.

Then, comparing operation 5550 depicts comparing the generated measuredreactor core parameter distribution to at least one reactor coreparameter distribution of a simulated operated nuclear reactor core. Forexample, FIGS. 1A through 3D, the one or more processors 106 ofcontroller 102 may generate a simulated operated nuclear reactor corerepresentative of an operated state of the initial simulated nuclearreactor core 120. In turn, the one or more processors 106 of thecontroller 102 may compare one or more generated measured reactor coreparameter distributions to one or more reactor core parameterdistribution of the simulated operated nuclear reactor core.

Then, operation compliance determining step 5560 depicts determining anoperational compliance state of the core of the nuclear reactor usingthe comparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core. For example, FIGS. 1Athrough 3D, the one or more processors 106 of the controller 102determine an operational compliance state of the core 202 of the nuclearreactor 101 based on the results of the comparison between the one ormore generated measured reactor core parameter distributions and the oneor more reactor core parameter distributions of the simulated operatednuclear reactor core.

FIG. 56 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 56 illustrates example embodiments where theinitial loading distribution determining operation 5510 may include atleast one additional operation. Additional operations may includeoperation 5602 and/or 5604.

The operation 5602 illustrates determining an initial loadingdistribution of a core of a nuclear reactor utilizing a BOC simulationprocess to generate a simulated BOC thermal nuclear reactor core. Forexample, as shown in FIGS. 1A through 3D, one or more processors 106 ofthe controller 102 are configured to determine an initial loadingdistribution of a core of a nuclear utilizing a BOC simulation processto generate a simulated BOC thermal nuclear reactor core. For instance,the one or more processors 106 of controller 102 may implement aprocess, such as, but not limited to process 400 of the presentdisclosure in order to generate a simulated BOC thermal nuclear reactorcore.

In another embodiment, the operation 5604 illustrates determining aninitial loading distribution of a core of a nuclear reactor utilizing aBOC simulation process to generate a simulated BOC fast nuclear reactorcore. For example, as shown in FIGS. 1A through 3D, one or moreprocessors 106 of the controller 102 are configured to determine aninitial loading distribution of a core of a nuclear utilizing a BOCsimulation process to generate a simulated BOC fast nuclear reactorcore. For instance, the one or more processors 106 of controller 102 mayimplement a process, such as, but not limited to process 400 of thepresent disclosure in order to generate a simulated BOC fast nuclearreactor core.

FIG. 57 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 57 illustrates example embodiments where theinitial loading distribution determining operation 5510 may include atleast one additional operation. Additional operations may includeoperation 5702 and/or 5704.

The operation 5702 illustrates determining an initial loadingdistribution of a core of a nuclear reactor utilizing a BOC simulationprocess to generate a simulated BOC breed-and-burn nuclear reactor core.For example, as shown in FIGS. 1A through 3D, one or more processors 106of the controller 102 are configured to determine an initial loadingdistribution of a core of a nuclear utilizing a BOC simulation processto generate a simulated BOC breed-and-burn nuclear reactor core. Forinstance, the one or more processors 106 of controller 102 may implementa process, such as, but not limited to process 400 of the presentdisclosure in order to generate a simulated BOC breed-and-burn nuclearreactor core.

In another embodiment, the operation 5704 illustrates determining aninitial loading distribution of a core of a nuclear reactor utilizing aBOC simulation process to generate a simulated BOC traveling wavenuclear reactor core. For example, as shown in FIGS. 1A through 3D, oneor more processors 106 of the controller 102 are configured to determinean initial loading distribution of a core of a nuclear utilizing a BOCsimulation process to generate a simulated BOC traveling wave nuclearreactor core. For instance, the one or more processors 106 of controller102 may implement a process, such as, but not limited to process 400 ofthe present disclosure in order to generate a simulated BOC travelingwave nuclear reactor core.

FIG. 58 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 58 illustrates example embodiments where theinitial loading distribution determining operation 5510 may include atleast one additional operation. Additional operations may includeoperation 5802.

The operation 5802 illustrates determining an initial loadingdistribution of a nuclear reactor utilizing a beginning of cycle (BOC)simulation process, the BOC simulation process configured to determine aset of simulated positions of a set of regions within a simulated BOCnuclear reactor core suitable for reducing a deviation metric between atleast one reactor core parameter distribution of the simulated BOCnuclear reactor core and a received at least one reactor core parameterdistribution associated with a state of a core of a reference nuclearreactor below a selected tolerance level. For example, as shown in FIGS.1A through 3D, one or more processors 106 of the controller 102 areconfigured to determine an initial loading distribution of a nuclearreactor utilizing a beginning of cycle (BOC) simulation process, the BOCsimulation process configured to determine a set of simulated positionsof a set of regions within a simulated BOC nuclear reactor core suitablefor reducing a deviation metric between at least one reactor coreparameter distribution of the simulated BOC nuclear reactor core and areceived at least one reactor core parameter distribution associatedwith a state of a core of a reference nuclear reactor below a selectedtolerance level.

FIG. 59A illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 59A illustrates example embodiments where thearranging operation 5520 may include at least one additional operation.Additional operations may include operation 5902 and/or 5904.

The operation 5902 illustrates, responsive to the initial loadingdistribution determination, arranging at least one fuel assembly of thecore of the nuclear reactor according to the set of simulated positionsof the set of regions of the simulated BOC nuclear reactor core. Forexample, as shown in FIGS. 1A through 3D, upon determining the initialloading distribution of the simulated BOC core (e.g., simulated core120), one or more processors 106 of the controller 102 may direct thefuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of reactor 101 in accordance with the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For instance, upon determining the initial loading distribution ofthe simulated BOC core, one or more processors 106 of the controller 102may transmit a command signal 207 (see FIG. 2A) indicative of the set ofsimulated positions of the set of regions of the simulated BOC nuclearreactor core to the fuel handler controller 206. In turn, the fuelhandler controller 206 may transmit a command signal 209 encoded withinstructions necessary for the fuel handler 204 to arrange one or morefuel assemblies 208 of the reactor core 202 of reactor 101 in accordancewith the set of simulated positions of the set of regions of thesimulated BOC nuclear reactor core.

In another embodiment, the operation 5904 illustrates, responsive to auser input, arranging at least one fuel assembly of the core of thenuclear reactor according to the set of simulated positions of the setof regions of the simulated BOC nuclear reactor core. For example, asshown in FIGS. 1A through 3D, in response to a signal from a user inputdevice 118, one or more processors 106 of the controller 102 may directthe fuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of reactor 101 in accordance with the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For instance, upon receiving a command signal from a user inputdevice 118 indicative of a user selection, one or more processors 106 ofthe controller 102 may transmit a command signal 207 (see FIG. 2A)indicative of the set of simulated positions of the set of regions ofthe simulated BOC nuclear reactor core to the fuel handler controller206. In turn, the fuel handler controller 206 may transmit a commandsignal 209 encoded with instructions necessary for the fuel handler 204to arrange one or more fuel assemblies 208 of the reactor core 202 ofreactor 101 in accordance with the set of simulated positions of the setof regions of the simulated BOC nuclear reactor core.

FIG. 59B illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 59B illustrates example embodiments where thearranging operation 5520 may include at least one additional operation.Additional operations may include operation 5906 and/or 5908.

The operation 5906 illustrates arranging at least one fuel assembly of acore of a thermal nuclear reactor according to the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For example, as shown in FIGS. 1A through 3D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 toarrange one or more fuel assemblies 208 of the reactor core 202 of athermal nuclear reactor in accordance with the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For instance, one or more processors 106 of the controller 102 maytransmit a command signal 207 indicative of the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore to the fuel handler controller 206. In turn, the fuel handlercontroller 206 may transmit a command signal 209 encoded withinstructions necessary for the fuel handler 204 to arrange one or morefuel assemblies 208 of the reactor core 202 of a thermal nuclear reactorin accordance with the set of simulated positions of the set of regionsof the simulated BOC nuclear reactor core.

In another embodiment, the operation 5908 illustrates arranging at leastone fuel assembly of a core of a fast nuclear reactor according to theset of simulated positions of the set of regions of the simulated BOCnuclear reactor core. For example, as shown in FIGS. 1A through 3D, oneor more processors 106 of the controller 102 may direct the fuel handler204 to arrange one or more fuel assemblies 208 of the reactor core 202of a fast nuclear reactor in accordance with the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For instance, one or more processors 106 of the controller 102 maytransmit a command signal 207 indicative of the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore to the fuel handler controller 206. In turn, the fuel handlercontroller 206 may transmit a command signal 209 encoded withinstructions necessary for the fuel handler 204 to arrange one or morefuel assemblies 208 of the reactor core 202 of a fast nuclear reactor inaccordance with the set of simulated positions of the set of regions ofthe simulated BOC nuclear reactor core.

FIG. 59C illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 59C illustrates example embodiments where thearranging operation 5520 may include at least one additional operation.Additional operations may include operation 5910 and/or 5912.

The operation 5910 illustrates arranging at least one fuel assembly of acore of a breed-and-burn nuclear reactor according to the set ofsimulated positions of the set of regions of the simulated BOC nuclearreactor core. For example, as shown in FIGS. 1A through 3D, one or moreprocessors 106 of the controller 102 may direct the fuel handler 204 toarrange one or more fuel assemblies 208 of the reactor core 202 of abreed-and-burn nuclear reactor in accordance with the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore. For instance, one or more processors 106 of the controller 102 maytransmit a command signal 207 indicative of the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore to the fuel handler controller 206. In turn, the fuel handlercontroller 206 may transmit a command signal 209 encoded withinstructions necessary for the fuel handler 204 to arrange one or morefuel assemblies 208 of the reactor core 202 of a breed-and-burn nuclearreactor in accordance with the set of simulated positions of the set ofregions of the simulated BOC nuclear reactor core.

In another embodiment, the operation 5912 illustrates arranging at leastone fuel assembly of a core of a traveling wave nuclear reactoraccording to the set of simulated positions of the set of regions of thesimulated BOC nuclear reactor core. For example, as shown in FIGS. 1Athrough 3D, one or more processors 106 of the controller 102 may directthe fuel handler 204 to arrange one or more fuel assemblies 208 of thereactor core 202 of a traveling wave nuclear reactor in accordance withthe set of simulated positions of the set of regions of the simulatedBOC nuclear reactor core. For instance, one or more processors 106 ofthe controller 102 may transmit a command signal 207 indicative of theset of simulated positions of the set of regions of the simulated BOCnuclear reactor core to the fuel handler controller 206. In turn, thefuel handler controller 206 may transmit a command signal 209 encodedwith instructions necessary for the fuel handler 204 to arrange one ormore fuel assemblies 208 of the reactor core 202 of a traveling wavenuclear reactor in accordance with the set of simulated positions of theset of regions of the simulated BOC nuclear reactor core.

FIG. 59D illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 59D illustrates example embodiments where thearranging operation 5520 may include at least one additional operation.Additional operations may include operation 5914 and/or 5916.

The operation 5914 illustrates translating at least one fuel assembly ofthe core of the nuclear reactor from an initial location to a subsequentlocation according to the set of simulated positions of a set of regionsof the simulated BOC nuclear reactor core. For example, as shown inFIGS. 1A through 3D, one or more processors 106 of the controller 102may direct the fuel handler 204 to translate one or more fuel assemblies208 of the core 202 of the nuclear reactor 101 from an initial locationto a subsequent location according to the set of simulated positions ofthe set of regions of the simulated BOC nuclear reactor core. Forinstance, one or more processors 106 of the controller 102 may directthe gripper 214 of fuel handler 204 to withdraw a selected fuel assembly212 and move the selected fuel assembly to a new location within thenuclear reactor core 202 according to the set of simulated positions ofthe set of regions of the simulated BOC nuclear reactor core.

In another embodiment, the operation 5916 illustrates replacing at leastone fuel assembly of the core of the nuclear reactor according to theset of simulated positions of a set of regions of the simulated BOCnuclear reactor core. For example, as shown in FIGS. 1A through 3D, oneor more processors 106 of the controller 102 may direct the fuel handler204 to replace one or more fuel assemblies 208 of the core 202 of thenuclear reactor 101 according to the set of simulated positions of a setof regions of the simulated BOC nuclear reactor core. For instance, oneor more processors 106 of the controller 102 may direct the gripper 214of fuel handler 204 to withdraw a selected fuel assembly 212 and movethe selected fuel assembly to a storage location outside of the reactorcore 202. In turn, the one or more processors 106 may direct the gripper214 (or an additional gripper) to insert a new fuel assembly into thereactor core 202 at the location of the removed fuel assembly 212. It isnoted herein that by repeating this process the system 300 may form (orre-assemble) the reactor core 202 in accordance with the set ofsimulated positions of the set of regions of the simulated BOC nuclearreactor core.

FIG. 60 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 60 illustrates example embodiments where thegenerating operation 5540 may include at least one additional operation.Additional operations may include operation 6002.

The operation 6002 illustrates generating a measured reactor coreparameter distribution utilizing at least one measurement of at leastone state variable at one or more locations within the core of thenuclear reactor. For example, as shown in FIGS. 1A through 3D, thesystem 300 may include a reactor core measurement system 302 configuredto measure one or more state variable (e.g., temperature, rate-of-changeof temperature, pressure, rate-of-change of pressure, neutron flux,rate-of-change of neutron flux and the like) values at one or morelocations within the nuclear reactor core 202. Then, based on themeasurements from the reactor core measurement system 302, the one ormore processors 106 of the controller 102 may generate a measuredreactor core parameter distribution. For instance, based on one or moremeasured values acquired by the reactor core measurement system 302, theone or more processors 106 of controller 102 may generate at least oneof a measured power density distribution, a measured power densityrate-of-change distribution, a measured reactivity distribution and ameasured reactivity rate-of-change distribution.

FIG. 61A illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 61A illustrates example embodiments where thecomparing operation 5550 may include at least one additional operation.Additional operations may include operation 6102.

The operation 6102 illustrates comparing the generated measured reactorcore parameter distribution to at least one reactor core parameterdistribution of a simulated operated nuclear reactor core, the simulatedoperated nuclear reactor core generated utilizing at least the initialloading distribution. For example, as shown in FIGS. 1A through 3D, theone or more processors 106 of controller 102 may generate a simulatedoperated core representative of an operational stat of the initialsimulated core 120, described previously herein. In this regard, the oneor more processors 106 may utilize the initial loading distribution ofreactor core 202 as an input to the model routine implemented todetermine the time-evolved simulated operate core. It is recognizedherein that the initial loading distribution of reactor core 202 maycorrespond with the simulated BOC core 120, as described previouslyherein. Then, the one or more processors 106 may compare the generatedmeasured reactor core parameter distribution to the one or more reactorcore parameter distributions of the simulated operated nuclear reactorcore.

FIG. 61B illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 61B illustrates example embodiments where thecomparing operation 5550 may include at least one additional operation.Additional operations may include operation 6104.

The operation 6104 illustrates calculating a deviation metric betweenthe generated measured reactor core parameter distribution and at leastone reactor core parameter distribution of a simulated operated nuclearreactor core. For example, as shown in FIGS. 1A through 3D, the one ormore processors 106 of controller 102 may calculate a deviation metricbetween the generated measured reactor core parameter distribution andthe one or more reactor core parameter distributions of the simulatedoperated nuclear reactor core. Further, the deviation metric mayinclude, but is not limited to, a difference (e.g., difference at acommon position), a relative difference, a ratio, an averaged difference(e.g., spatially averaged difference), maximum difference (e.g., maximumdifference between any two or more common positions), minimum difference(e.g., minimum difference between two or more common positions),aggregated deviation (e.g., global deviation metric) or any otherdeviation metric known in the art.

FIG. 62 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 62 illustrates example embodiments where thecomparing operation 5550 may include at least one additional operation.Additional operations may include operation 6202 and/or 6204.

The operation 6202 illustrates comparing the generated measured reactorcore power density distribution to at least one reactor core powerdensity distribution of a simulated operated nuclear reactor core. Forexample, as shown in FIGS. 1A through 3D, the one or more processors 106of controller 102 may generate a power density distribution for asimulated operated core representative of a time-lapsed operationalstate of the initial simulated core 120, described previously herein.Then, the one or more processors 106 may compare the generated measuredreactor core power density distribution to the one or more reactor corepower density distributions of the simulated operated nuclear reactorcore.

In another embodiment, the operation 6204 illustrates comparing thegenerated measured reactor core power density rate-of-changedistribution to at least one reactor core power density rate-of-changedistribution of a simulated operated nuclear reactor core. For example,as shown in FIGS. 1A through 3D, the one or more processors 106 ofcontroller 102 may generate a power density rate-of-change distributionfor a simulated operated core representative of a time-lapsedoperational state of the initial simulated core 120. Then, the one ormore processors 106 may compare the generated measured reactor corepower density rate-of-change distribution to the one or more reactorcore power density rate-of-change distributions of the simulatedoperated nuclear reactor core.

FIG. 63 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 63 illustrates example embodiments where thecomparing operation 5550 may include at least one additional operation.Additional operations may include operation 6302 and/or 6304.

The operation 6302 illustrates comparing the generated measured reactorcore reactivity distribution to at least one reactor core reactivitydistribution of a simulated operated nuclear reactor core. For example,as shown in FIGS. 1A through 3D, the one or more processors 106 ofcontroller 102 may generate a reactivity distribution for a simulatedoperated core representative of a time-lapsed operational state of theinitial simulated core 120. Then, the one or more processors 106 maycompare the generated measured reactor core reactivity distribution tothe one or more reactor core reactivity distributions of the simulatedoperated nuclear reactor core.

In another embodiment, the operation 6304 illustrates comparing thegenerated measured reactor core reactivity rate-of-change distributionto at least one reactor core reactivity rate-of-change distribution of asimulated operated nuclear reactor core. For example, as shown in FIGS.1A through 3D, the one or more processors 106 of controller 102 maygenerate a reactivity rate-of-change distribution for a simulatedoperated core representative of a time-lapsed operational state of theinitial simulated core 120. Then, the one or more processors 106 maycompare the generated measured reactor core reactivity rate-of-changedistribution to the one or more reactor core reactivity rate-of-changedistributions of the simulated operated nuclear reactor core.

FIG. 64 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 64 illustrates example embodiments where theoperational compliance determining operation 5560 may include at leastone additional operation. Additional operations may include operation6402.

The operation 6402 illustrates determining an operational compliancestate using the comparison between the generated measured reactor coreparameter distribution and the at least one reactor core parameterdistribution of the simulated operated nuclear reactor core, wherein adeviation metric between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core below a selected tolerancelevel corresponds to an in-compliance state. For example, the one ormore processors 106 of controller 102 may determine whether a deviationmetric calculated between the generated measured reactor core parameterdistribution and the one or more reactor core parameter distributions ofthe simulated operated nuclear reactor core corresponds to anin-compliance state. For instance, a determination that the deviationmetric is at or below the selected tolerance level may correspond withan in-compliance state for the nuclear reactor core 202.

FIG. 65 illustrates alternative embodiments of the example operationalflow 5500 of FIG. 55. FIG. 65 illustrates example embodiments where theoperational compliance determining operation 5560 may include at leastone additional operation. Additional operations may include operation6502.

The operation 6502 illustrates determining an operational compliancestate using the comparison between the generated measured reactor coreparameter distribution and the at least one reactor core parameterdistribution of the simulated operated nuclear reactor core, wherein adeviation metric between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core above a selected tolerancelevel corresponds to an out-of-compliance state. For example, as shownin FIGS. 1A-3D, the one or more processors 106 of controller 102 maydetermine whether a deviation metric calculated between the generatedmeasured reactor core parameter distribution and the one or more reactorcore parameter distributions of the simulated operated nuclear reactorcore corresponds to an out-of-compliance state. For instance, adetermination that the deviation metric above the selected tolerancelevel may correspond with an out-of-compliance state for the nuclearreactor core 202.

FIG. 66 illustrates an operational flow 6600 representing exampleoperations related to determining an operation compliance state of acore of a nuclear reactor. FIG. 66 illustrates an example embodimentwhere the example operational flow 6600 of FIG. 66 may include at leastone additional operation. Additional operations may include anadditional loading distribution determining step 6602.

The operation 6602 illustrates, responsive to a determination of anout-of-compliance state, determining an additional loading distributionof the core of the nuclear reactor utilizing an additional simulationprocess, the additional simulation process configured to determine a setof simulated positions of a set of regions within an additionalsimulated core suitable for reducing the deviation metric between atleast one reactor core parameter distribution of the additionalsimulated core and the received at least one reactor core parameterdistribution associated with a state of a core of a reference nuclearreactor below a selected tolerance level. For example, as shown in FIGS.1A-3D, the one or more processors 106 of controller 102 may determine anadditional loading distribution of the core 202 via an additional coresimulation process configured to determine a set of simulated positionsof a set of regions within an additional simulated core suitable forreducing the deviation metric between one or more reactor core parameterdistributions of the additional simulated core and the received one ormore reactor core parameter distributions associated with a state (e.g.,equilibrium state) of a core of a reference nuclear reactor below aselected tolerance level.

FIG. 67 illustrates an operational flow 6700 representing exampleoperations related to determining an operation compliance state of acore of a nuclear reactor. FIG. 67 illustrates an example embodimentwhere the example operational flow 6700 of FIG. 67 may include at leastone additional operation. Additional operations may include an arrangingstep 6702.

The operation 6702 illustrates, responsive to the additional loadingdistribution determination, arranging at least one fuel assembly of thecore of the core of the nuclear reactor according to the set ofsimulated positions of the set of regions of the simulated additionalcore. For example, as shown in FIGS. 1A through 3D, upon determining theadditional loading distribution of the additional simulated core, one ormore processors 106 of the controller 102 may direct the fuel handler204 to arrange one or more fuel assemblies 208 of the reactor core 202of reactor 101 in accordance with the set of simulated positions of theset of regions of the additional simulated core of a nuclear reactorcore. For instance, upon determining the initial additional distributionof the additional simulated core, one or more processors 106 of thecontroller 102 may transmit a command signal 307 (see FIG. 3A)indicative of the set of simulated positions of the set of regions ofadditional simulated core of a nuclear reactor to the fuel handlercontroller 206. In turn, the fuel handler controller 206 may transmit acommand signal 309 encoded with instructions necessary for the fuelhandler 204 to arrange one or more fuel assemblies 208 of the reactorcore 202 of reactor 101 in accordance with the set of simulatedpositions of the set of regions of the additional simulated nuclearreactor core.

FIG. 68 illustrates an operational flow 6800 representing exampleoperations related to determining an operation compliance state of acore of a nuclear reactor. FIG. 68 illustrates an example embodimentwhere the example operational flow 6800 of FIG. 68 may include at leastone additional operation. Additional operations may include reportingoperations 6802, 6804, 6806 and/or 6808.

The operation 6802 illustrates reporting the operation compliance stateof the core of the nuclear reactor. For example, as shown in FIGS. 1Athrough 3D, the one or more processors 106 of controller 102 may reportthe operation compliance state of the core of the nuclear reactor to adestination. For instance, the one or more processors 106 of controller102 may transmit one or more signals indicative of the operationalcompliance state of the core 202 of the nuclear reactor 101 to adestination.

In another embodiment, the operation 6804 illustrates reporting theoperation compliance state of the core of the nuclear reactor of thecore of the nuclear reactor to a display. For example, as shown in FIGS.1A through 3D, the one or more processors 106 of controller 102 mayreport the operation compliance state of the core of the nuclear reactorto a display (e.g., audio or visual display). For instance, the one ormore processors 106 of controller 102 may transmit one or more signalsindicative of the operational compliance state of the core 202 of thenuclear reactor 101 to a display unit 116.

In another embodiment, the operation 6806 illustrates reporting theoperation compliance state of the core of the nuclear reactor of thecore of the nuclear reactor to a memory. For example, as shown in FIGS.1A through 3D, the one or more processors 106 of controller 102 mayreport the operation compliance state of the core of the nuclear reactorto a memory device. For instance, the one or more processors 106 ofcontroller 102 may transmit one or more signals indicative of theoperational compliance state of the core 202 of the nuclear reactor 101to a memory device 108.

In another embodiment, the operation 6806 illustrates reporting theoperation compliance state of the core of the nuclear reactor to acontrol system of the nuclear reactor. For example, as shown in FIGS. 1Athrough 3D, the one or more processors 106 of controller 102 may reportthe operation compliance state of the core of the nuclear reactor tocontrol system 180 of the nuclear reactor 101. For instance, the one ormore processors 106 of controller 102 may transmit one or more signalsindicative of the operational compliance state of the core 202 of thenuclear reactor 101 to control system 180 of the nuclear reactor 101.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware. Hence, thereare several possible vehicles by which the processes and/or devicesand/or other technologies described herein may be effected, none ofwhich is inherently superior to the other in that any vehicle to beutilized is a choice dependent upon the context in which the vehiclewill be deployed and the specific concerns (e.g., speed, flexibility, orpredictability) of the implementer, any of which may vary. Those skilledin the art will recognize that optical aspects of implementations willtypically employ optically-oriented hardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device-detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operations described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled//implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.).

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof.Consequently, as used herein “electro-mechanical system” includes, butis not limited to, electrical circuitry operably coupled with atransducer (e.g., an actuator, a motor, a piezoelectric crystal, a MicroElectro Mechanical System (MEMS), etc.), electrical circuitry having atleast one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of memory(e.g., random access, flash, read only, etc.)), electrical circuitryforming a communications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs. Those skilled in the art willalso appreciate that examples of electro-mechanical systems include butare not limited to a variety of consumer electronics systems, medicaldevices, as well as other systems such as motorized transport systems,factory automation systems, security systems, and/orcommunication/computing systems. Those skilled in the art will recognizethat electro-mechanical as used herein is not necessarily limited to asystem that has both electrical and mechanical actuation except ascontext may dictate otherwise.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

Although a user is shown/described herein as a single illustratedfigure, those skilled in the art will appreciate that the user may berepresentative of a human user, a robotic user (e.g., computationalentity), and/or substantially any combination thereof (e.g., a user maybe assisted by one or more robotic agents) unless context dictatesotherwise. Those skilled in the art will appreciate that, in general,the same may be said of “sender” and/or other entity-oriented terms assuch terms are used herein unless context dictates otherwise.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

In some instances, one or more components may be referred to herein as“configured to,” “configurable to,” “operable/operative to,”“adapted/adaptable,” “able to,” “conformable/conformed to,” etc. Thoseskilled in the art will recognize that such terms (e.g., “configuredto”) can generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.

With respect to the appended claims, those skilled in the art willappreciate that recited operations therein may generally be performed inany order. Also, although various operational flows are presented in asequence(s), it should be understood that the various operations may beperformed in other orders than those which are illustrated, or may beperformed concurrently. Examples of such alternate orderings may includeoverlapping, interleaved, interrupted, reordered, incremental,preparatory, supplemental, simultaneous, reverse, or other variantorderings, unless context dictates otherwise. Furthermore, terms like“responsive to,” “related to,” or other past-tense adjectives aregenerally not intended to exclude such variants, unless context dictatesotherwise.

1. A method, comprising: determining an initial loading distribution ofa core of a nuclear reactor utilizing a beginning-of-cycle (BOC)simulation process to generate a simulated BOC nuclear reactor core;arranging at least one fuel assembly of the core of the nuclear reactoraccording to a set of simulated positions of a set of regions of thesimulated BOC nuclear reactor core; operating the core of the nuclearreactor for a selected time interval; generating a measured reactor coreparameter distribution utilizing at least one measurement of at leastone reactor core parameter at one or more locations within the core ofthe nuclear reactor; comparing the generated measured reactor coreparameter distribution to at least one reactor core parameterdistribution of a simulated operated nuclear reactor core; anddetermining an operational compliance state of the core of the nuclearreactor using the comparison between the generated measured reactor coreparameter distribution and the at least one reactor core parameterdistribution of the simulated operated nuclear reactor core.
 2. Themethod of claim 1, wherein the determining an initial loadingdistribution of a core of a nuclear reactor utilizing abeginning-of-cycle (BOC) simulation process to generate a simulated BOCnuclear reactor core includes: determining an initial loadingdistribution of a core of a nuclear reactor utilizing abeginning-of-cycle (BOC) simulation process to generate at least one ofa simulated BOC thermal nuclear reactor core, a simulated BOC fastnuclear reactor core, a simulated BOC breed-and-burn nuclear reactorcore and a simulated BOC traveling wave nuclear reactor core.
 3. Themethod of claim 1, wherein the determining an initial loadingdistribution of a nuclear reactor utilizing a beginning-of-cycle (BOC)simulation process includes: determining an initial loading distributionof a core of a nuclear reactor utilizing a beginning-of-cycle (BOC)simulation process, the BOC simulation process configured to determine aset of simulated positions of a set of regions within a simulated BOCnuclear reactor core suitable for reducing a deviation metric between atleast one reactor core parameter distribution of the simulated BOCnuclear reactor core and the received at least one reactor coreparameter distribution associated with a state of a core of a referencenuclear reactor below a selected tolerance level.
 4. The method of claim1, wherein the determining an operational compliance state using thecomparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core includes: determining anoperational compliance state using the comparison between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core, wherein a deviation metric between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor corebelow a selected tolerance level corresponds to an in-compliance state.5. The method of claim 1, wherein the determining an operationalcompliance state using the comparison between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor coreincludes: determining an operational compliance state using thecomparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core, wherein a deviation metricbetween the generated measured reactor core parameter distribution andthe at least one reactor core parameter distribution of the simulatedoperated nuclear reactor core above a selected tolerance levelcorresponds to an out-of-compliance state.
 6. The method of claim 5,further comprising: responsive to a determination of anout-of-compliance state, determining an additional loading distributionof the core of the nuclear reactor utilizing an additional simulationprocess, the additional simulation process configured to determine a setof simulated positions of a set of regions within an additionalsimulated core suitable for reducing the deviation metric between atleast one reactor core parameter distribution of the additionalsimulated core and the received at least one reactor core parameterdistribution associated with a state of a core of a reference nuclearreactor below a selected tolerance level.
 7. The method of claim 6,further comprising: responsive to the additional loading distributiondetermination, arranging at least one fuel assembly of the core of thecore of the nuclear reactor according to the set of simulated positionsof the set of regions of the additional simulated core.
 8. The method ofclaim 1, further comprising: reporting the operation compliance state ofthe core of the nuclear reactor.
 9. The method of claim 1, wherein thearranging at least one fuel assembly of the core of the nuclear reactoraccording to a set of simulated positions of a set of regions of thesimulated BOC nuclear reactor core includes: responsive to the initialloading distribution determination, arranging at least one fuel assemblyof the core of the nuclear reactor according to the set of simulatedpositions of the set of regions of the simulated BOC nuclear reactorcore.
 10. (canceled)
 11. The method of claim 1, wherein the arranging atleast one fuel assembly of the core of the nuclear reactor according toa set of simulated positions of a set of regions of the simulated BOCnuclear reactor core includes: arranging at least one fuel assembly of acore of at least one of a thermal reactor, a fast nuclear reactor, abreed-and-burn reactor and a traveling wave reactor according to the setof simulated positions of the set of regions of the simulated BOCnuclear reactor core.
 12. The method of claim 1, wherein the arrangingat least one fuel assembly of the core of the nuclear reactor accordingto a set of simulated positions of a set of regions of the simulated BOCnuclear reactor core includes: translating at least one fuel assembly ofthe core of the nuclear reactor from an initial location to a subsequentlocation according to the set of simulated positions of a set of regionsof the simulated BOC nuclear reactor core.
 13. The method of claim 1,wherein the arranging at least one fuel assembly of the core of thenuclear reactor according to a set of simulated positions of a set ofregions of the simulated BOC nuclear reactor core includes: replacing atleast one fuel assembly of the core of the nuclear reactor according tothe set of simulated positions of a set of regions of the simulated BOCnuclear reactor core.
 14. The method of claim 1, wherein the generatinga measured reactor core parameter distribution utilizing at least onemeasurement of at least reactor core parameter at one or more locationswithin the core of the nuclear reactor includes: generating a measuredreactor core parameter distribution utilizing at least one measurementof at least one state variable at one or more locations within the coreof the nuclear reactor.
 15. The method of claim 1, wherein the comparingthe generated measured reactor core parameter distribution to at leastone reactor core parameter distribution of a simulated operated nuclearreactor core includes: comparing the generated measured reactor coreparameter distribution to at least one reactor core parameterdistribution of a simulated operated nuclear reactor core, the simulatedoperated nuclear reactor core generated utilizing at least the initialloading distribution.
 16. The method of claim 1, wherein the comparingthe generated measured reactor core parameter distribution to at leastone reactor core parameter distribution of a simulated operated nuclearreactor core includes: calculating a deviation metric between thegenerated measured reactor core parameter distribution and at least onereactor core parameter distribution of a simulated operated nuclearreactor core.
 17. The method of claim 1, wherein the comparing thegenerated measured reactor core parameter distribution to at least onereactor core parameter distribution of a simulated operated nuclearreactor core includes: comparing a generated measured reactor core powerdensity distribution to at least one reactor core power densitydistribution of a simulated operated nuclear reactor core.
 18. Themethod of claim 1, wherein the comparing the generated measured reactorcore parameter distribution to at least one reactor core parameterdistribution of a simulated operated nuclear reactor core includes:comparing a generated measured reactor core rate of change of a powerdensity distribution to at least one reactor core rate of change of apower density distribution of a simulated operated nuclear reactor core.19. The method of claim 1, wherein the comparing the generated measuredreactor core parameter distribution to at least one reactor coreparameter distribution of a simulated operated nuclear reactor coreincludes: comparing a generated measured reactivity distribution to atleast one reactor core reactivity distribution of a simulated operatednuclear reactor core
 20. The method of claim 1, wherein the comparingthe generated measured reactor core parameter distribution to at leastone reactor core parameter distribution of a simulated operated nuclearreactor core includes: comparing a generated measured reactor core rateof change of a reactivity distribution to at least one reactor core rateof change of reactivity distribution of a simulated operated nuclearreactor core.
 21. A non-transitory computer-readable medium comprisingprogram instructions, wherein the program instructions are executableto: determine an initial loading distribution of a core of a nuclearreactor utilizing a beginning-of-cycle (BOC) simulation process togenerate a simulated BOC nuclear reactor core; arrange at least one fuelassembly of the core of the nuclear reactor according to a set ofsimulated positions of a set of regions of the simulated BOC nuclearreactor core; operate the core of the nuclear reactor for a selectedtime interval; generate a measured reactor core parameter distributionutilizing at least one measurement of at least one reactor coreparameter at one or more locations within the core of the nuclearreactor; compare the generated measured reactor core parameterdistribution to at least one reactor core parameter distribution of asimulated operated nuclear reactor core; and determine an operationalcompliance state of the core of the nuclear reactor using the comparisonbetween the generated measured reactor core parameter distribution andthe at least one reactor core parameter distribution of the simulatedoperated core.
 22. The non-transitory computer-readable medium of claim21, wherein the determining an initial loading distribution of a core ofa nuclear reactor utilizing a beginning-of-cycle (BOC) simulationprocess to generate a simulated BOC nuclear reactor core includes:determining an initial loading distribution of a core of a nuclearreactor utilizing a beginning-of-cycle (BOC) simulation process togenerate at least one of a simulated BOC thermal nuclear reactor core, asimulated BOC fast nuclear reactor core, a simulated BOC breed-and-burnnuclear reactor core and a simulated BOC traveling wave nuclear reactorcore.
 23. The non-transitory computer-readable medium of claim 21,wherein the determining an initial loading distribution of a core of anuclear reactor utilizing a beginning-of-cycle (BOC) simulation processto generate a simulated BOC nuclear reactor core includes: determiningan initial loading distribution of a core of a nuclear reactor utilizinga beginning-of-cycle (BOC) simulation process, the BOC simulationprocess configured to determine a set of simulated positions of a set ofregions within a simulated BOC nuclear reactor core suitable forreducing a deviation metric between at least one reactor core parameterdistribution of the simulated BOC nuclear reactor core and the receivedat least one reactor core parameter distribution associated with a stateof a core of a reference nuclear reactor below a selected tolerancelevel.
 24. The non-transitory computer-readable medium of claim 21,wherein the determining an operational compliance state of the core ofthe nuclear reactor using the comparison between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated core includes:determining an operational compliance state using the comparison betweenthe generated measured reactor core parameter distribution and the atleast one reactor core parameter distribution of the simulated operatednuclear reactor core, wherein a deviation metric between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core below a selected tolerance level corresponds to anin-compliance state.
 25. The non-transitory computer-readable medium ofclaim 21, wherein the determining an operational compliance state usingthe comparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core includes: determining anoperational compliance state using the comparison between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core, wherein a deviation metric between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor coreabove a selected tolerance level corresponds to an out-of-compliancestate.
 26. The non-transitory computer-readable medium of claim 25,further comprising: responsive to a determination of anout-of-compliance state, determining an additional loading distributionof the core of the nuclear reactor utilizing an additional simulationprocess, the additional simulation process configured to determine a setof simulated positions of a set of regions within an additionalsimulated core suitable for reducing the deviation metric between atleast one reactor core parameter distribution of the additionalsimulated core and the received at least one reactor core parameterdistribution associated with a state of a core of a reference nuclearreactor below a selected tolerance level.
 27. The non-transitorycomputer-readable medium of claim 26, further comprising: responsive tothe additional loading distribution determination, arranging at leastone fuel assembly of the core of the core of the nuclear reactoraccording to the set of simulated positions of the set of regions of theadditional simulated core.
 28. (canceled)
 29. (canceled)
 30. (canceled)31. (canceled)
 32. (canceled)
 33. (canceled)
 34. (canceled) 35.(canceled)
 36. (canceled)
 37. (canceled)
 38. (canceled)
 39. (canceled)40. A nuclear reactor system, comprising: a nuclear reactor including anuclear reactor core, the nuclear reactor core including a plurality offuel assemblies; and a controller configured to: determine an initialloading distribution of the nuclear reactor core utilizing abeginning-of-cycle (BOC) simulation process to generate a simulated BOCnuclear reactor core; generate a measured reactor core parameterdistribution utilizing at least one measurement of at least one reactorcore parameter at one or more locations within the core of the nuclearreactor, following operation of the nuclear reactor for a selected timeinterval; compare the generated measured reactor core parameterdistribution to at least one reactor core parameter distribution of asimulated operated nuclear reactor core generated utilizing at least theinitial loading distribution; and determine an operational compliancestate of the core of the nuclear reactor using the comparison betweenthe generated measured reactor core parameter distribution and the atleast one reactor core parameter distribution of the simulated operatednuclear reactor core, wherein the plurality of fuel assemblies of thenuclear reactor core are arrangeable according to a set of simulatedpositions of a set of regions of at least one of the simulated BOCnuclear reactor core and an additional simulated operated nuclearreactor core.
 41. The nuclear reactor system of claim 40, wherein thedetermining an initial loading distribution of the core of the nuclearreactor utilizing a beginning-of-cycle (BOC) simulation process togenerate a simulated BOC nuclear reactor core includes: determining aninitial loading distribution of the core of the nuclear reactorutilizing a beginning-of-cycle (BOC) simulation process, the BOCsimulation process configured to determine a set of simulated positionsof a set of regions within a simulated BOC nuclear reactor core suitablefor reducing a deviation metric between at least one reactor coreparameter distribution of the simulated BOC nuclear reactor core and thereceived at least one reactor core parameter distribution associatedwith a state of a core of a reference nuclear reactor below a selectedtolerance level.
 42. The nuclear reactor system of claim 40, wherein thedetermining an operational compliance state of the core of the nuclearreactor using the comparison between the generated measured reactor coreparameter distribution and the at least one reactor core parameterdistribution of the simulated operated nuclear reactor core includes:determining an operational compliance state using the comparison betweenthe generated measured reactor core parameter distribution and the atleast one reactor core parameter distribution of the simulated operatednuclear reactor core, wherein a deviation metric between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core below a selected tolerance level corresponds to anin-compliance state.
 43. The nuclear reactor system of claim 40, whereinthe determining an operational compliance state of the core of thenuclear reactor using the comparison between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor coreincludes: determining an operational compliance state using thecomparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core, wherein a deviation metricbetween the generated measured reactor core parameter distribution andthe at least one reactor core parameter distribution of the simulatedoperated nuclear reactor core above a selected tolerance levelcorresponds to an out-of-compliance state.
 44. The nuclear reactorsystem of claim 43, wherein the controller is further configured to:responsive to a determination of an out-of-compliance state, determinean additional loading distribution of the core of the nuclear reactorutilizing an additional simulation process, the additional simulationprocess configured to determine a set of simulated positions of a set ofregions within the additional simulated core suitable for reducing thedeviation metric between at least one reactor core parameterdistribution of the additional simulated core and a received at leastone reactor core parameter distribution associated with a state of acore of a reference nuclear reactor below a selected tolerance level.45. The nuclear reactor system of claim 40, further comprising: a fuelassembly handler configured to arrange at least one fuel assembly of thecore of the nuclear reactor according to the set of simulated positionsof the set of regions of at least one of the simulated BOC nuclearreactor core and the additional simulated nuclear reactor core.
 46. Thenuclear reactor system of claim 45, wherein the fuel assembly handlerconfigured to arrange at least one fuel assembly of the core of thenuclear reactor according to the set of simulated positions of the setof regions of at least one of the simulated BOC nuclear reactor core andthe additional simulated nuclear reactor core includes: a fuel assemblyhandler communicatively coupled to the controller, the fuel assemblyhandler configured to arrange at least one fuel assembly of the core ofthe nuclear reactor according to the set of simulated positions of theset of regions of at least one of the simulated BOC nuclear reactor coreand the additional simulated nuclear reactor core, in response to asignal from a user interface device.
 47. The nuclear reactor system ofclaim 45, wherein the fuel assembly handler configured to arrange atleast one fuel assembly of the core of the nuclear reactor according tothe set of simulated positions of the set of regions of at least one ofthe simulated BOC nuclear reactor core and the additional simulatednuclear reactor core includes: a fuel assembly handler communicativelycoupled to the controller, the fuel assembly handler configured toarrange at least one fuel assembly of the core of the nuclear reactoraccording to the set of simulated positions of the set of regions of thesimulated BOC nuclear reactor core, in response to the initial loadingdistribution determination.
 48. The nuclear reactor system of claim 45,wherein the fuel assembly handler configured to arrange at least onefuel assembly of the core of the nuclear reactor according to the set ofsimulated positions of the set of regions of at least one of thesimulated BOC nuclear reactor core and the additional simulated nuclearreactor core includes: a fuel assembly handler communicatively coupledto the controller, the fuel assembly handler configured to arrange atleast one fuel assembly of the core of the nuclear reactor according tothe set of simulated positions of the set of regions of the additionalsimulated nuclear reactor core, in response to the additional loadingdistribution determination.
 49. (canceled)
 50. (canceled)
 51. Thenuclear reactor system of claim 40, wherein the determining anoperational compliance state of the core of the nuclear reactor usingthe comparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core includes: determining anoperational compliance state using the comparison between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core, wherein a deviation metric between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor corebelow a selected tolerance level corresponds to an in-compliance state.52. The nuclear reactor system of claim 40, wherein the determining anoperational compliance state of the core of the nuclear reactor usingthe comparison between the generated measured reactor core parameterdistribution and the at least one reactor core parameter distribution ofthe simulated operated nuclear reactor core includes: determining anoperational compliance state using the comparison between the generatedmeasured reactor core parameter distribution and the at least onereactor core parameter distribution of the simulated operated nuclearreactor core, wherein a deviation metric between the generated measuredreactor core parameter distribution and the at least one reactor coreparameter distribution of the simulated operated nuclear reactor coreabove a selected tolerance level corresponds to an out-of-compliancestate.
 53. The nuclear reactor system of claim 52, wherein thecontroller is further configured to: responsive to a determination of anout-of-compliance state, determine an additional loading distribution ofthe core of the nuclear reactor utilizing an additional simulationprocess, the additional simulation process configured to determine a setof simulated positions of a set of regions within the additionalsimulated core suitable for reducing the deviation metric between atleast one reactor core parameter distribution of the additionalsimulated core and a received at least one reactor core parameterdistribution associated with a state of a core of a reference nuclearreactor below a selected tolerance level.
 54. The nuclear reactor systemof claim 40, wherein the nuclear reactor includes: at least one of athermal nuclear reactor, a fast nuclear reactor, a breed-and-burnnuclear reactor and a traveling wave nuclear reactor.
 55. (canceled) 56.The nuclear reactor system of claim 40, wherein the comparing thegenerated measured reactor core parameter distribution to at least onereactor core parameter distribution of a simulated operated nuclearreactor core includes: comparing a generated measured reactor core powerdensity distribution to at least one reactor core power densitydistribution of a simulated operated nuclear reactor core
 57. Thenuclear reactor system of claim 40, wherein the comparing the generatedmeasured reactor core parameter distribution to at least one reactorcore parameter distribution of a simulated operated nuclear reactor coreincludes: calculating a deviation metric between the generated measuredreactor core distribution and at least one reactor core distribution ofa simulated operated nuclear reactor core.
 58. (canceled)
 59. (canceled)60. (canceled)
 61. The nuclear reactor system of claim 40, wherein atleast a portion of the simulated operated nuclear reactor core includesat least one of recycled nuclear fuel, unburned nuclear fuel andenriched nuclear fuel.
 62. The nuclear reactor system of claim 40,wherein the simulated operated nuclear reactor core includes a pluralityof simulated fuel assemblies.
 63. The nuclear reactor system of claim40, further comprising: a reactor core measurement system operablycoupled to the core of the nuclear reactor and communicatively coupledto the controller.
 64. The nuclear reactor system of claim 63, whereinthe reactor core measurement system is configured to perform at leastone measurement of at least one state variable at one or more locationswithin the core of the nuclear reactor.
 65. The nuclear reactor systemof claim 64, wherein the controller is further configured to generatethe measured reactor core parameter distribution utilizing the at leastone measurement of at least one state variable at one or more locationswithin the core of the nuclear reactor from the reactor core measurementsystem.